{ "mode": "man", "parameter": "muttrc", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/muttrc/5/json", "generated": "2026-06-16T10:00:08Z", "sections": { "NAME": { "content": "muttrc - Configuration file for the Mutt Mail User Agent\n", "subsections": [] }, "DESCRIPTION": { "content": "A mutt configuration file consists of a series of “commands”. Each line of the file may con‐\ntain one or more commands. When multiple commands are used, they must be separated by a\nsemicolon (“;”).\n\nThe hash mark, or pound sign (“#”), is used as a “comment” character. You can use it to anno‐\ntate your initialization file. All text after the comment character to the end of the line is\nignored.\n\nSingle quotes (“'”) and double quotes (“\"”) can be used to quote strings which contain spaces\nor other special characters. The difference between the two types of quotes is similar to\nthat of many popular shell programs, namely that a single quote is used to specify a literal\nstring (one that is not interpreted for shell variables or quoting with a backslash [see next\nparagraph]), while double quotes indicate a string which should be evaluated. For example,\nbackticks are evaluated inside of double quotes, but not single quotes.\n\n\\ quotes the next character, just as in shells such as bash and zsh. For example, if want to\nput quotes (“\"”) inside of a string, you can use “\\” to force the next character to be a lit‐\neral instead of interpreted character.\n\n“\\\\” means to insert a literal “\\” into the line. “\\n” and “\\r” have their usual C meanings\nof linefeed and carriage-return, respectively.\n\nA “\\” at the end of a line can be used to split commands over multiple lines, provided that\nthe split points don't appear in the middle of command names.\n\nIt is also possible to substitute the output of a Unix command in an initialization file.\nThis is accomplished by enclosing the command in backticks (`command`).\n\nUNIX environment variables can be accessed like the way it is done in shells like sh and\nbash: Prepend the name of the variable by a dollar (“$”) sign.\n", "subsections": [] }, "COMMANDS": { "content": "alias [-group name [...]] key address [, address [ ... ]]\nunalias [ * | key ]\n\nalias defines an alias key for the given addresses. Each address will be resolved into\neither an email address (user@example.com) or a named email address (User Name\n). The address may be specified in either format, or in the format\n“user@example.com (User Name)”. unalias removes the alias corresponding to the given\nkey or all aliases when “*” is used as an argument. The optional -group argument to\nalias causes the aliased address(es) to be added to the named group.\n\ngroup [-group name] [-rx EXPR [ ... ]] [-addr address [ ... ]]\nungroup [-group name ] [ * | [[-rx EXPR [ ... ]] [-addr address [ ... ]]]\n\ngroup is used to directly add either addresses or regular expressions to the specified\ngroup or groups. The different categories of arguments to the group command can be in\nany order. The flags -rx and -addr specify what the following strings (that cannot be‐\ngin with a hyphen) should be interpreted as: either a regular expression or an email\naddress, respectively. ungroup is used to remove addresses or regular expressions\nfrom the specified group or groups. The syntax is similar to the group command, how‐\never the special character * can be used to empty a group of all of its contents.\n\nThese address groups can also be created implicitly by the alias, lists, subscribe and\nalternates commands by specifying the optional -group option.\n\nOnce defined, these address groups can be used in patterns to search for and limit the\ndisplay to messages matching a group.\n\nalternates [-group name] regexp [ regexp [ ... ]]\nunalternates [ * | regexp [ regexp [ ... ]] ]\n\nalternates is used to inform mutt about alternate addresses where you receive mail;\nyou can use regular expressions to specify alternate addresses. This affects mutt's\nidea about messages from you, and messages addressed to you. unalternates removes a\nregular expression from the list of known alternates. The -group flag causes all of\nthe subsequent regular expressions to be added to the named group.\n\nalternativeorder type[/subtype] [ ... ]\nunalternativeorder [ * | type/subtype] [...]\n\nalternativeorder command permits you to define an order of preference which is used\nby mutt to determine which part of a multipart/alternative body to display. A subtype\nof “*” matches any subtype, as does an empty subtype. unalternativeorder removes\nentries from the ordered list or deletes the entire list when “*” is used as an argu‐\nment.\n\nattachments [ + | - ]disposition mime-type\nunattachments [ + | - ]disposition mime-type", "subsections": [ { "name": "attachments ?", "content": "unattachments *\n\nattachments specifies what kinds of attachments are used for Mutt's attachment count‐\ning and searching support.\n\ndisposition is the attachment's Content-Disposition type - either inline or attach‐\nment. You can abbreviate this to I or A.\n\nThe first part of a message or multipart group, if inline, is counted separately than\nother inline parts. Specify root or R for disposition to count these as attachments.\nIf this first part is of type multipart/alternative, note that its top-level inline\nparts are also counted via root disposition (if $countalternatives is set).\n\ndisposition is prefixed by either a + symbol or a - symbol. If it's a +, you're saying\nthat you want to allow this disposition and MIME type to qualify. If it's a -, you're\nsaying that this disposition and MIME type is an exception to previous + rules.\n\nmime-type is the MIME type of the attachment you want the command to affect. A MIME\ntype is always of the format major/minor, where major describes the broad category of\ndocument you're looking at, and minor describes the specific type within that cate‐\ngory. The major part of mime-type must be literal text (or the special token *), but\nthe minor part may be a regular expression. (Therefore, */.* matches any MIME type.)\n\nThe MIME types you give to the attachments directive are a kind of pattern. When you\nuse the attachments directive, the patterns you specify are added to a list. When you\nuse unattachments, the pattern is removed from the list. The patterns are not expanded\nand matched to specific MIME types at this time - they're just text in a list. They're\nonly matched when actually evaluating a message.\n\nautoview type[/subtype] [ ... ]\nunautoview type[/subtype] [ ... ]\n\nThis commands permits you to specify that mutt should automatically convert the given\nMIME types to text/plain when displaying messages. For this to work, there must be a\nmailcap(5) entry for the given MIME type with the copiousoutput flag set. A subtype\nof “*” matches any subtype, as does an empty subtype.\n\nmimelookup type[/subtype] [ ... ]\nunmimelookup type[/subtype] [ ... ]\n\nThis command permits you to define a list of \"data\" MIME content types for which mutt\nwill try to determine the actual file type from the file name, and not use a mail‐‐\ncap(5) entry given for the original MIME type. For instance, you may add the applica‐‐\ntion/octet-stream MIME type to this list.\n\nbind map1,map2,... key function\nThis command binds the given key for the given map or maps to the given function. Mul‐\ntiple maps may be specified by separating them with commas (no whitespace is allowed).\n\nValid maps are: generic, alias, attach, browser, editor, index, compose, pager, pgp,\npostpone, mix.\n\nFor more information on keys and functions, please consult the Mutt Manual. Note that\nthe function name is to be specified without angle brackets.\n\naccount-hook [!]regexp command\nThis hook is executed whenever you access a remote mailbox. Useful to adjust configu‐\nration settings to different IMAP or POP servers.\n\ncharset-hook alias charset\nThis command defines an alias for a character set. This is useful to properly display\nmessages which are tagged with a character set name not known to mutt.\n\niconv-hook charset local-charset\nThis command defines a system-specific name for a character set. This is useful when\nyour system's iconv(3) implementation does not understand MIME character set names\n(such as iso-8859-1), but instead insists on being fed with implementation-specific\ncharacter set names (such as 8859-1). In this specific case, you'd put this into your\nconfiguration file:\n\niconv-hook iso-8859-1 8859-1\n\nmessage-hook [!]pattern command\nBefore mutt displays (or formats for replying or forwarding) a message which matches\nthe given pattern (or, when it is preceded by an exclamation mark, does not match the\npattern), the given command is executed. When multiple message-hooks match, they are\nexecuted in the order in which they occur in the configuration file.\n\nfolder-hook [!]regexp command\nWhen mutt enters a folder which matches regexp (or, when regexp is preceded by an ex‐\nclamation mark, does not match regexp), the given command is executed.\n\nWhen several folder-hooks match a given mail folder, they are executed in the order\ngiven in the configuration file.\n\nmacro map key sequence [ description ]\nThis command binds the given sequence of keys to the given key in the given map or\nmaps. For valid maps, see bind. To specify multiple maps, put only a comma between\nthe maps.\n\ncolor object [ attribute ... ] foreground background [ regexp ]\ncolor index [ attribute ... ] foreground background [ pattern ]\ncolor compose composeobject [ attribute ... ] foreground background\nuncolor index pattern [ pattern ... ]\n\nIf your terminal supports color, these commands can be used to assign foreground/back‐\nground combinations to certain objects. Valid objects are: attachment, body, bold,\nerror, header, hdrdefault, index, indicator, markers, message, normal, prompt, quoted,\nquotedN, search, signature, status, tilde, tree, underline. If the sidebar is enabled\nthe following objects are also valid: sidebardivider, sidebarflagged, sidebarhigh‐‐\nlight, sidebarindicator, sidebarnew, sidebarspoolfile. The body and header objects\nallow you to restrict the colorization to a regular expression. The index object per‐\nmits you to select colored messages by pattern.\n\nValid composeobjects include header, securityencrypt, securitysign, securityboth,\nsecuritynone.\n\nValid colors include: white, black, green, magenta, blue, cyan, yellow, red, default,\ncolorN.\n\nValid attributes include: none, bold, underline, reverse, and standout.\n\nmono object attribute [ regexp ]\nmono index attribute [ pattern ]\n\nFor terminals which don't support color, you can still assign attributes to objects.\n\n[un]ignore pattern [ pattern ... ]\nThe ignore command permits you to specify header fields which you usually don't wish\nto see. Any header field whose tag begins with an “ignored” pattern will be ignored.\n\nThe unignore command permits you to define exceptions from the above mentioned list of\nignored headers.\n\nlists [-group name] regexp [ regexp ... ]\nunlists regexp [ regexp ... ]\nsubscribe [-group name] regexp [ regexp ... ]\nunsubscribe regexp [ regexp ... ]\n\nMutt maintains two lists of mailing list address patterns, a list of subscribed mail‐\ning lists, and a list of known mailing lists. All subscribed mailing lists are known.\nPatterns use regular expressions.\n\nThe lists command adds a mailing list address to the list of known mailing lists. The\nunlists command removes a mailing list from the lists of known and subscribed mailing\nlists. The subscribe command adds a mailing list to the lists of known and subscribed\nmailing lists. The unsubscribe command removes it from the list of subscribed mailing\nlists. The -group flag adds all of the subsequent regular expressions to the named\ngroup.\n\nmbox-hook [!]regexp mailbox\nWhen mutt changes to a mail folder which matches regexp, mailbox will be used as the\n“mbox” folder, i.e., read messages will be moved to that folder when the mail folder\nis left.\n\nThe first matching mbox-hook applies.\n\nmailboxes [[-notify | -nonotify]\n[-poll | -nopoll]\n[[-label label] | -nolabel]\nfilename] [ ... ]\nunmailboxes [ * | filename ... ]\n\nThe mailboxes specifies folders which can receive mail and which will be checked for\nnew messages. When changing folders, pressing space will cycle through folders with\nnew mail. The unmailboxes command is used to remove a file name from the list of\nfolders which can receive mail. If \"*\" is specified as the file name, the list is\nemptied.\n\nmyhdr string\nunmyhdr field\n\nUsing myhdr, you can define headers which will be added to the messages you compose.\nunmyhdr will remove the given user-defined headers.\n\nhdrorder header1 header2 [ ... ]\nWith this command, you can specify an order in which mutt will attempt to present\nheaders to you when viewing messages.\n\nsave-hook [!]pattern filename\nWhen a message matches pattern, the default file name when saving it will be the given\nfilename.\n\nfcc-hook [!]pattern filename\nWhen an outgoing message matches pattern, the default file name for storing a copy\n(fcc) will be the given filename.\n\nfcc-save-hook [!]pattern filename\nThis command is an abbreviation for identical fcc-hook and save-hook commands.\n\nsend-hook [!]pattern command\nWhen composing a message matching pattern, command is executed. When multiple send-\nhooks match, they are executed in the order in which they occur in the configuration\nfile.\n\nsend2-hook [!]pattern command\nWhenever a message matching pattern is changed (either by editing it or by using the\ncompose menu), command is executed. When multiple send2-hooks match, they are executed\nin the order in which they occur in the configuration file. Possible applications in‐\nclude setting the $sendmail variable when a message's from header is changed.\n\nsend2-hook execution is not triggered by use of enter-command from the compose menu.\n\nreply-hook [!]pattern command\nWhen replying to a message matching pattern, command is executed. When multiple re‐‐\nply-hooks match, they are executed in the order in which they occur in the configura‐\ntion file, but all reply-hooks are matched and executed before send-hooks, regardless\nof their order in the configuration file.\n\ncrypt-hook regexp key-id\nThe crypt-hook command provides a method by which you can specify the ID of the public\nkey to be used when encrypting messages to a certain recipient. The meaning of \"key\nID\" is to be taken broadly: This can be a different e-mail address, a numerical key\nID, or even just an arbitrary search string. You may use multiple crypt-hooks with\nthe same regexp; multiple matching crypt-hooks result in the use of multiple key-ids\nfor a recipient.\n\nindex-format-hook name [!]pattern format-string\nThis command is used to inject format strings dynamically into $indexformat based on\npattern matching against the current message.\n\nThe $indexformat expando %@name@ specifies a placeholder for the injection. Index-\nformat-hooks with the same name are matched using pattern against the current message.\nMatching is done in the order specified in the .muttrc, with the first match being\nused. The hook's format-string is then substituted and evaluated.\n\nopen-hook regexp \"command\"\nclose-hook regexp \"command\"\nappend-hook regexp \"command\"\n\nThese commands provide a way to handle compressed folders. The given regexp specifies\nwhich folders are taken as compressed (e.g. \"\\\\.gz$\"). The commands tell Mutt how to\nuncompress a folder (open-hook), compress a folder (close-hook) or append a compressed\nmail to a compressed folder (append-hook). The command string is the printf(3) like\nformat string, and it should accept two parameters: %f, which is replaced with the\n(compressed) folder name, and %t which is replaced with the name of the temporary\nfolder to which to write.\n\npush string\nexec function [ ... ]\n\npush adds the named string to the keyboard buffer. “exec function” is equivalent to\n“push ”.\n\nrun MuttLisp\n\nThe run command evaluates the MuttLisp argument. The output of the MuttLisp is then\nexecuted as a Mutt command, as if it were typed in the muttrc instead.\n\nscore pattern value\nunscore [ * | pattern ... ]\n\nThe score commands adds value to a message's score if pattern matches it. The unscore\ncommand removes score entries from the list.\n\nset [no|inv|&|?]variable[=value] [ ... ]\ntoggle variable [ ... ]\nunset variable [ ... ]\nreset variable [ ... ]\n\nThese commands are used to set and manipulate configuration variables.\n\nMutt knows four basic types of variables: boolean, number, string and quadoption.\nBoolean variables can be set (true), unset (false), or toggled. Number variables can\nbe assigned a positive integer value.\n\nString variables consist of any number of printable characters. Strings must be en‐\nclosed in quotes if they contain spaces or tabs. You may also use the “C” escape se‐\nquences \\n and \\t for newline and tab, respectively.\n\nQuadoption variables are used to control whether or not to be prompted for certain ac‐\ntions, or to specify a default action. A value of yes will cause the action to be\ncarried out automatically as if you had answered yes to the question. Similarly, a\nvalue of no will cause the action to be carried out as if you had answered “no.” A\nvalue of ask-yes will cause a prompt with a default answer of “yes” and ask-no will\nprovide a default answer of “no.”\n\nThe reset command resets all given variables to the compile time defaults. If you re‐\nset the special variable all, all variables will reset to their compile time defaults.\n\nsetenv [?]variable [ value ]\nunsetenv variable\n\nThese alter the environment that Mutt passes on to its child processes. You can also\nquery current environment values by prefixing a “?” character.\n\nsidebarwhitelist mailbox [ mailbox ...]\nunsidebarwhitelist [ * | mailbox ... ]\n\nsidebarwhitelist specifies mailboxes that will always be displayed in the sidebar,\neven if $sidebarnewmailonly is set and the mailbox does not contain new mail.\n\nunsidebarwhitelist is used to remove a mailbox from the list of whitelisted mail‐\nboxes. Use unsidebarwhitelist * to remove all mailboxes.\n\nsource filename\nThe given file will be evaluated as a configuration file.\n\nspam pattern format\nnospam pattern\n\nThese commands define spam-detection patterns from external spam filters, so that mutt\ncan sort, limit, and search on ``spam tags'' or ``spam attributes'', or display them\nin the index. See the Mutt manual for details.\n\nsubjectrx pattern replacement\nunsubjectrx [ * | pattern ]\n\nsubjectrx specifies a regular expression pattern which, if detected in a message sub‐\nject, causes the subject to be replaced with the replacement value. The replacement is\nsubject to substitutions in the same way as for the spam command: %L for the text to\nthe left of the match, %R for text to the right of the match, and %1 for the first\nsubgroup in the match (etc). If you simply want to erase the match, set it to “%L%R”.\nAny number of subjectrx commands may coexist.\n\nNote this well: the replacement value replaces the entire subject, not just the match!\n\nunsubjectrx removes a given subjectrx from the substitution list. If * is used as the\npattern, all substitutions will be removed.\n\nunhook [ * | hook-type ]\nThis command will remove all hooks of a given type, or all hooks when “*” is used as\nan argument. hook-type can be any of the -hook commands documented above.\n\nmailtoallow header-field [ ... ]\nunmailtoallow [ * | header-field ... ]\n\nThese commands allow the user to modify the list of allowed header fields in a mailto:\nURL that Mutt will include in the the generated message. By default the list contains\nonly subject and body, as specified by RFC2368.\n\necho message\nPrints message to the message window. After printing the message, echo will pause for\nthe number of seconds specified by $sleeptime.\n\ncd directory\nChanges the current working directory.\n" } ] }, "PATTERNS": { "content": "In various places with mutt, including some of the above mentioned hook commands, you can\nspecify patterns to match messages.\n", "subsections": [ { "name": "Constructing Patterns", "content": "A simple pattern consists of a modifier of the form “~character”, possibly followed by a pa‐\nrameter against which mutt is supposed to match the object specified by this modifier. For\nsome characters, the ~ may be replaced by another character to alter the behavior of the\nmatch. These are described in the list of modifiers, below.\n\nWith some of these modifiers, the object to be matched consists of several e-mail addresses.\nIn these cases, the object is matched if at least one of these e-mail addresses matches. You\ncan prepend a hat (“^”) character to such a pattern to indicate that all addresses must match\nin order to match the object.\n\nYou can construct complex patterns by combining simple patterns with logical operators. Log‐\nical AND is specified by simply concatenating two simple patterns, for instance “~C mutt-dev\n~s bug”. Logical OR is specified by inserting a vertical bar (“|”) between two patterns, for\ninstance “~C mutt-dev | ~s bug”. Additionally, you can negate a pattern by prepending a bang\n(“!”) character. For logical grouping, use braces (“()”). Example: “!(~t mutt|~c mutt) ~f\nelkins”.\n" }, { "name": "Simple Patterns", "content": "Mutt understands the following simple patterns:\n\n~A all messages\n~b EXPR messages which contain EXPR in the message body.\n=b STRING If IMAP is enabled, like ~b but searches for STRING on the server, rather than\ndownloading each message and searching it locally.\n~B EXPR messages which contain EXPR in the whole message.\n=B STRING If IMAP is enabled, like ~B but searches for STRING on the server, rather than\ndownloading each message and searching it locally.\n~c EXPR messages carbon-copied to EXPR\n%c GROUP messages carbon-copied to any member of GROUP\n~C EXPR messages either to: or cc: EXPR\n%C GROUP messages either to: or cc: to any member of GROUP\n~d MIN-MAX messages with “date-sent” in a Date range\n~D deleted messages\n~e EXPR messages which contain EXPR in the “Sender” field\n%e GROUP messages which contain a member of GROUP in the “Sender” field\n~E expired messages\n~f EXPR messages originating from EXPR\n%f GROUP messages originating from any member of GROUP\n~F flagged messages\n~g PGP signed messages\n~G PGP encrypted messages\n~h EXPR messages which contain EXPR in the message header\n=h STRING If IMAP is enabled, like ~h but searches for STRING on the server, rather than\ndownloading each message and searching it locally. STRING must be of the form\n“header: substring”\n~H EXPR messages with spam tags matching EXPR\n~i EXPR messages which match EXPR in the “Message-ID” field\n~k messages containing PGP key material\n~l messages addressed to a known mailing list (defined by either subscribe or list)\n~L EXPR messages either originated or received by EXPR\n%L GROUP messages either originated or received by any member of GROUP\n~m MIN-MAX message in the range MIN to MAX\n~M EXPR messages which contain a mime Content-Type matching EXPR\n~n MIN-MAX messages with a score in the range MIN to MAX\n~N new messages\n~O old messages\n~p messages addressed to you (consults $from, alternates, and local account/hostname\ninformation)\n~P messages from you (consults $from, alternates, and local account/hostname infor‐\nmation)\n~Q messages which have been replied to\n~r MIN-MAX messages with “date-received” in a Date range\n~R read messages\n~s EXPR messages having EXPR in the “Subject” field.\n~S superseded messages\n~t EXPR messages addressed to EXPR\n~T tagged messages\n~u messages addressed to a subscribed mailing list (defined by subscribe commands)\n~U unread messages\n~v message is part of a collapsed thread.\n~V cryptographically verified messages\n~x EXPR messages which contain EXPR in the “References” or “In-Reply-To” field\n~X MIN-MAX messages with MIN - MAX attachments\n~y EXPR messages which contain EXPR in the “X-Label” field\n~z MIN-MAX messages with a size in the range MIN to MAX\n~= duplicated messages (see $duplicatethreads)\n~$ unreferenced message (requires threaded view)\n~(PATTERN) messages in threads containing messages matching a certain pattern, e.g. all\nthreads containing messages from you: ~(~P)\n~<(PATTERN) messages whose immediate parent matches PATTERN, e.g. replies to your messages:\n~<(~P)\n~>(PATTERN) messages having an immediate child matching PATTERN, e.g. messages you replied\nto: ~>(~P)\n\nIn the above, EXPR is a regular expression.\n\nWith the ~d, ~m, ~n, ~r, ~X, and ~z modifiers, you can also specify ranges in the forms MIN, MIN-, and -MAX.\n\nWith the ~z modifier, the suffixes “K” and “M” are allowed to specify kilobyte and megabyte\nrespectively.\n\nThe ~b, ~B, ~h, ~M, and ~X modifiers require reading each message in, which can be much\nslower.\n\nYou can force Mutt to treat EXPR as a simple string instead of a regular expression by using\n= instead of ~ in the pattern name.\n" }, { "name": "Matching dates", "content": "The ~d and ~r modifiers are used to match date ranges, which are interpreted to be given in\nyour local time zone.\n\nA date is of the form DD[/MM[/[cc]YY]], that is, a two-digit date, optionally followed by a\ntwo-digit month, optionally followed by a year specifications. Omitted fields default to the\ncurrent month and year.\n\nMutt understands either two or four digit year specifications. When given a two-digit year,\nmutt will interpret values less than 70 as lying in the 21st century (i.e., “38” means 2038\nand not 1938, and “00” is interpreted as 2000), and values greater than or equal to 70 as ly‐\ning in the 20th century.\n\nNote that this behavior is Y2K compliant, but that mutt does have a Y2.07K problem.\n\nAlternatively, you may use YYYYMMDD to specify a date.\n\nIf a date range consists of a single date, the modifier in question will match that precise\ndate. If the date range consists of a dash (“-”), followed by a date, this range will match\nany date before and up to the date given. Similarly, a date followed by a dash matches the\ndate given and any later point of time. Two dates, separated by a dash, match any date which\nlies in the given range of time.\n\nYou can also modify any absolute date by giving an error range. An error range consists of\none of the characters +, -, *, followed by a positive number, followed by one of the unit\ncharacters y, m, w, or d, specifying a unit of years, months, weeks, or days. + increases\nthe maximum date matched by the given interval of time, - decreases the minimum date matched\nby the given interval of time, and * increases the maximum date and decreases the minimum\ndate matched by the given interval of time. It is possible to give multiple error margins,\nwhich cumulate. Example: 1/1/2001-1w+2w*3d\n\nYou can also specify offsets relative to the current date. An offset is specified as one of\nthe characters <, >, =, followed by a positive number, followed by one of the unit characters\ny, m, w, d, H, M, or S. > matches dates which are older than the specified amount of time,\nan offset which begins with the character < matches dates which are more recent than the\nspecified amount of time, and an offset which begins with the character = matches points of\ntime which are precisely the given amount of time ago.\n" } ] }, "CONFIGURATION VARIABLES": { "content": "abortnoattach\nType: quadoption\nDefault: no\n\nWhen the body of the message matches $abortnoattachregexp and there are no attach‐\nments, this quadoption controls whether to abort sending the message.\n\n\n\nabortnoattachregexp\nType: regular expression\nDefault: “attach”\n\nSpecifies a regular expression to match against the body of the message, to determine\nif an attachment was mentioned but mistakenly forgotten. If it matches, $abortnoat‐\ntach will be consulted to determine if message sending will be aborted.\n\nLike other regular expressions in Mutt, the search is case sensitive if the pattern\ncontains at least one upper case letter, and case insensitive otherwise.\n\n\n\nabortnosubject\nType: quadoption\nDefault: ask-yes\n\nIf set to yes, when composing messages and no subject is given at the subject prompt,\ncomposition will be aborted. If set to no, composing messages with no subject given\nat the subject prompt will never be aborted.\n\n\n\nabortunmodified\nType: quadoption\nDefault: yes\n\nIf set to yes, composition will automatically abort after editing the message body if\nno changes are made to the file (this check only happens after the first edit of the\nfile). When set to no, composition will never be aborted.\n\n\n\naliasfile\nType: path\nDefault: “~/.muttrc”\n\nThe default file in which to save aliases created by the function. En‐\ntries added to this file are encoded in the character set specified by $configcharset\nif it is set or the current character set otherwise.\n\nNote: Mutt will not automatically source this file; you must explicitly use the\n“source” command for it to be executed in case this option points to a dedicated alias\nfile.\n\nThe default for this option is the currently used muttrc file, or “~/.muttrc” if no\nuser muttrc was found.\n\n\n\naliasformat\nType: string\nDefault: “%4n %2f %t %-10a %r”\n\nSpecifies the format of the data displayed for the “alias” menu. The following\nprintf(3)-style sequences are available:\n%a alias name\n%f flags - currently, a “d” for an alias marked for deletion\n%n index number\n%r address which alias expands to\n%t character which indicates if the alias is tagged for inclusion\n\n\nallow8bit\nType: boolean\nDefault: yes\n\nControls whether 8-bit data is converted to 7-bit using either Quoted- Printable or\nBase64 encoding when sending mail.\n\n\n\nallowansi\nType: boolean\nDefault: no\n\nControls whether ANSI color codes in messages (and color tags in rich text messages)\nare to be interpreted. Messages containing these codes are rare, but if this option\nis set, their text will be colored accordingly. Note that this may override your color\nchoices, and even present a security problem, since a message could include a line\nlike\n\n\n[-- PGP output follows ...\n\n\nand give it the same color as your attachment color (see also $crypttimestamp).\n\n\n\narrowcursor\nType: boolean\nDefault: no\n\nWhen set, an arrow (“->”) will be used to indicate the current entry in menus instead\nof highlighting the whole line. On slow network or modem links this will make re‐\nsponse faster because there is less that has to be redrawn on the screen when moving\nto the next or previous entries in the menu.\n\n\n\nasciichars\nType: boolean\nDefault: no\n\nIf set, Mutt will use plain ASCII characters when displaying thread and attachment\ntrees, instead of the default ACS characters.\n\n\n", "subsections": [ { "name": "askbcc", "content": "Type: boolean\nDefault: no\n\nIf set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before editing an\noutgoing message.\n\n\n" }, { "name": "askcc", "content": "Type: boolean\nDefault: no\n\nIf set, Mutt will prompt you for carbon-copy (Cc) recipients before editing the body\nof an outgoing message.\n\n\n\nassumedcharset\nType: string\nDefault: “”\n\nThis variable is a colon-separated list of character encoding schemes for messages\nwithout character encoding indication. Header field values and message body content\nwithout character encoding indication would be assumed that they are written in one of\nthis list. By default, all the header fields and message body without any charset in‐\ndication are assumed to be in “us-ascii”.\n\nFor example, Japanese users might prefer this:\n\n\nset assumedcharset=”iso-2022-jp:euc-jp:shiftjis:utf-8”\n\n\nHowever, only the first content is valid for the message body.\n\n\n\nattachcharset\nType: string\nDefault: “”\n\nThis variable is a colon-separated list of character encoding schemes for text file\nattachments. Mutt uses this setting to guess which encoding files being attached are\nencoded in to convert them to a proper character set given in $sendcharset.\n\nIf unset, the value of $charset will be used instead. For example, the following con‐\nfiguration would work for Japanese text handling:\n\n\nset attachcharset=”iso-2022-jp:euc-jp:shiftjis:utf-8”\n\n\nNote: for Japanese users, “iso-2022-*” must be put at the head of the value as shown\nabove if included.\n\n\n\nattachformat\nType: string\nDefault: “%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] ”\n\nThis variable describes the format of the “attachment” menu. The following\nprintf(3)-style sequences are understood:\n%C charset\n%c requires charset conversion (“n” or “c”)\n%D deleted flag\n%d description (if none, falls back to %F)\n%e MIME content-transfer-encoding\n%F filename in content-disposition header (if none, falls back to %f)\n%f filename\n%I disposition (“I” for inline, “A” for attachment)\n%m major MIME type\n%M MIME subtype\n%n attachment number\n%Q “Q”, if MIME part qualifies for attachment counting\n%s size (see formatstrings-size)\n%t tagged flag\n%T graphic tree characters\n%u unlink (=to delete) flag\n%X number of qualifying MIME parts in this part and its children (please see the\n“attachments” section for possible speed effects)\n%>X right justify the rest of the string and pad with character “X”\n%|X pad to the end of the line with character “X”\n%*X soft-fill with character “X” as pad\n\nFor an explanation of “soft-fill”, see the $indexformat documentation.\n\n\n\nattachsavedir\nType: path\nDefault: “”\n\nThe default directory to save attachments from the “attachment” menu. If it doesn't\nexist, Mutt will prompt to create the directory before saving.\n\nIf the path is invalid (e.g. not a directory, or cannot be chdir'ed to), Mutt will\nfall back to using the current directory.\n\n\n\nattachsep\nType: string\nDefault: “\\n”\n\nThe separator to add between attachments when operating (saving, printing, piping,\netc) on a list of tagged attachments.\n\n\n\nattachsplit\nType: boolean\nDefault: yes\n\nIf this variable is unset, when operating (saving, printing, piping, etc) on a list of\ntagged attachments, Mutt will concatenate the attachments and will operate on them as\na single attachment. The $attachsep separator is added after each attachment. When\nset, Mutt will operate on the attachments one by one.\n\n\n" }, { "name": "attribution", "content": "Type: string (localized)\nDefault: “On %d, %n wrote:”\n\nThis is the string that will precede a message which has been included in a reply.\nFor a full listing of defined printf(3)-like sequences see the section on $indexfor‐\nmat.\n\n\n\nattributionlocale\nType: string\nDefault: “”\n\nThe locale used by strftime(3) to format dates in the attribution string. Legal val‐\nues are the strings your system accepts for the locale environment variable $LCTIME.\n\nThis variable is to allow the attribution date format to be customized by recipient or\nfolder using hooks. By default, Mutt will use your locale environment, so there is no\nneed to set this except to override that default.\n\n\n\nautosubscribe\nType: boolean\nDefault: no\n\nWhen set, Mutt assumes the presence of a List-Post header means the recipient is sub‐\nscribed to the list. Unless the mailing list is in the “unsubscribe” or “unlist”\nlists, it will be added to the “subscribe” list. Parsing and checking these things\nslows header reading down, so this option is disabled by default.\n\n\n\nautotag\nType: boolean\nDefault: no\n\nWhen set, functions in the index menu which affect a message will be applied to all\ntagged messages (if there are any). When unset, you must first use the \nfunction (bound to “;” by default) to make the next function apply to all tagged mes‐\nsages.\n\n\n" }, { "name": "autocrypt", "content": "Type: boolean\nDefault: no\n\nWhen set, enables autocrypt, which provides passive encryption protection with keys\nexchanged via headers. See “autocryptdoc” for more details. (Autocrypt only)\n\n\n\nautocryptacctformat\nType: string\nDefault: “%4n %-30a %20p %10s”\n\nThis variable describes the format of the “autocrypt account” menu. The following\nprintf(3)-style sequences are understood\n%a email address\n%k gpg keyid\n%n current entry number\n%p prefer-encrypt flag\n%s status flag (active/inactive)\n\n(Autocrypt only)\n\n\n\nautocryptdir\nType: path\nDefault: “~/.mutt/autocrypt”\n\nThis variable sets where autocrypt files are stored, including the GPG keyring and\nsqlite database. See “autocryptdoc” for more details. (Autocrypt only)\n\n\n\nautocryptreply\nType: boolean\nDefault: yes\n\nWhen set, replying to an autocrypt email automatically enables autocrypt in the reply.\nYou may want to unset this if you're using the same key for autocrypt as normal\nweb-of-trust, so that autocrypt isn't forced on for all encrypted replies. (Autocrypt\nonly)\n\n\n" }, { "name": "autoedit", "content": "Type: boolean\nDefault: no\n\nWhen set along with $editheaders, Mutt will skip the initial send-menu (prompting for\nsubject and recipients) and allow you to immediately begin editing the body of your\nmessage. The send-menu may still be accessed once you have finished editing the body\nof your message.\n\nNote: when this option is set, you cannot use send-hooks that depend on the recipients\nwhen composing a new (non-reply) message, as the initial list of recipients is empty.\n\nAlso see $fastreply.\n\n\n\nbackgroundedit\nType: boolean\nDefault: no\n\nWhen set, Mutt will run $editor in the background during message composition. A land‐\ning page will display, waiting for the $editor to exit. The landing page may be ex‐\nited, allowing perusal of the mailbox, or even for other messages to be composed.\nBackgrounded sessions may be returned to via the function.\n\nFor background editing to work properly, $editor must be set to an editor that does\nnot try to use the Mutt terminal: for example a graphical editor, or a script launch‐\ning (and waiting for) the editor in another Gnu Screen window.\n\nFor more details, see “bgedit” (”Background Editing” in the manual).\n\n\n\nbackgroundconfirmquit\nType: boolean\nDefault: yes\n\nWhen set, if there are any background edit sessions, you will be prompted to confirm\nexiting Mutt, in addition to the $quit prompt.\n\n\n\nbackgroundformat\nType: string\nDefault: “%10S %7p %s”\n\nThis variable describes the format of the “background compose” menu. The following\nprintf(3)-style sequences are understood:\n%i parent message id (for replies and forwarded messages)\n%n the running number on the menu\n%p pid of the $editor process\n%r comma separated list of “To:” recipients\n%R comma separated list of “Cc:” recipients\n%s subject of the message\n%S status of the $editor process: running/finished\n\n" }, { "name": "beep", "content": "Type: boolean\nDefault: yes\n\nWhen this variable is set, mutt will beep when an error occurs.\n\n\n\nbeepnew\nType: boolean\nDefault: no\n\nWhen this variable is set, mutt will beep whenever it prints a message notifying you\nof new mail. This is independent of the setting of the $beep variable.\n\n\n" }, { "name": "bounce", "content": "Type: quadoption\nDefault: ask-yes\n\nControls whether you will be asked to confirm bouncing messages. If set to yes you\ndon't get asked if you want to bounce a message. Setting this variable to no is not\ngenerally useful, and thus not recommended, because you are unable to bounce messages.\n\n\n\nbouncedelivered\nType: boolean\nDefault: yes\n\nWhen this variable is set, mutt will include Delivered-To headers when bouncing mes‐\nsages. Postfix users may wish to unset this variable.\n\n\n\nbraillefriendly\nType: boolean\nDefault: no\n\nWhen this variable is set, mutt will place the cursor at the beginning of the current\nline in menus, even when the $arrowcursor variable is unset, making it easier for\nblind persons using Braille displays to follow these menus. The option is unset by\ndefault because many visual terminals don't permit making the cursor invisible.\n\n\n\nbrowserabbreviatemailboxes\nType: boolean\nDefault: yes\n\nWhen this variable is set, mutt will abbreviate mailbox names in the browser mailbox\nlist, using '~' and '=' shortcuts.\n\nThe default ””alpha”” setting of $sortbrowser uses locale-based sorting (using str‐‐\ncoll(3)), which ignores some punctuation. This can lead to some situations where the\norder doesn't make intuitive sense. In those cases, it may be desirable to unset this\nvariable.\n\n\n\nbrowserstickycursor\nType: boolean\nDefault: yes\n\nWhen this variable is set, the browser will attempt to keep the cursor on the same\nmailbox when performing various functions. These include moving up a directory, tog‐\ngling between mailboxes and directory listing, creating/renaming a mailbox, toggling\nsubscribed mailboxes, and entering a new mask.\n\n\n\ncertificatefile\nType: path\nDefault: “~/.muttcertificates”\n\nThis variable specifies the file where the certificates you trust are saved. When an\nunknown certificate is encountered, you are asked if you accept it or not. If you ac‐\ncept it, the certificate can also be saved in this file and further connections are\nautomatically accepted.\n\nYou can also manually add CA certificates in this file. Any server certificate that is\nsigned with one of these CA certificates is also automatically accepted.\n\nExample:\n\n\nset certificatefile=~/.mutt/certificates\n\n\n\n\nchangefoldernext\nType: boolean\nDefault: no\n\nWhen this variable is set, the function mailbox suggestion will start\nat the next folder in your “mailboxes” list, instead of starting at the first folder\nin the list.\n\n\n" }, { "name": "charset", "content": "Type: string\nDefault: “”\n\nCharacter set your terminal uses to display and enter textual data. It is also the\nfallback for $sendcharset.\n\nUpon startup Mutt tries to derive this value from environment variables such as\n$LCCTYPE or $LANG.\n\nNote: It should only be set in case Mutt isn't able to determine the character set\nused correctly.\n\n\n\ncheckmboxsize\nType: boolean\nDefault: no\n\nWhen this variable is set, mutt will use file size attribute instead of access time\nwhen checking for new mail in mbox and mmdf folders.\n\nThis variable is unset by default and should only be enabled when new mail detection\nfor these folder types is unreliable or doesn't work.\n\nNote that enabling this variable should happen before any “mailboxes” directives occur\nin configuration files regarding mbox or mmdf folders because mutt needs to determine\nthe initial new mail status of such a mailbox by performing a fast mailbox scan when\nit is defined. Afterwards the new mail status is tracked by file size changes.\n\n\n\nchecknew\nType: boolean\nDefault: yes\n\nNote: this option only affects maildir and MH style mailboxes.\n\nWhen set, Mutt will check for new mail delivered while the mailbox is open. Espe‐\ncially with MH mailboxes, this operation can take quite some time since it involves\nscanning the directory and checking each file to see if it has already been looked at.\nIf this variable is unset, no check for new mail is performed while the mailbox is\nopen.\n\n\n\ncollapseunread\nType: boolean\nDefault: yes\n\nWhen unset, Mutt will not collapse a thread if it contains any unread messages.\n\n\n\ncomposeformat\nType: string (localized)\nDefault: “-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-”\n\nControls the format of the status line displayed in the “compose” menu. This string\nis similar to $statusformat, but has its own set of printf(3)-like sequences:\n%a total number of attachments\n%h local hostname\n%l approximate size (in bytes) of the current message (see formatstrings-size)\n%v Mutt version string\n\nSee the text describing the $statusformat option for more information on how to set\n$composeformat.\n\n\n\nconfigcharset\nType: string\nDefault: “”\n\nWhen defined, Mutt will recode commands in rc files from this encoding to the current\ncharacter set as specified by $charset and aliases written to $aliasfile from the\ncurrent character set.\n\nPlease note that if setting $charset it must be done before setting $configcharset.\n\nRecoding should be avoided as it may render unconvertable characters as question marks\nwhich can lead to undesired side effects (for example in regular expressions).\n\n\n" }, { "name": "confirmappend", "content": "Type: boolean\nDefault: yes\n\nWhen set, Mutt will prompt for confirmation when appending messages to an existing\nmailbox.\n\n\n" }, { "name": "confirmcreate", "content": "Type: boolean\nDefault: yes\n\nWhen set, Mutt will prompt for confirmation when saving messages to a mailbox which\ndoes not yet exist before creating it.\n\n\n\nconnecttimeout\nType: number\nDefault: 30\n\nCauses Mutt to timeout a network connection (for IMAP, POP or SMTP) after this many\nseconds if the connection is not able to be established. A negative value causes Mutt\nto wait indefinitely for the connection attempt to succeed.\n\n\n\ncontenttype\nType: string\nDefault: “text/plain”\n\nSets the default Content-Type for the body of newly composed messages.\n\n\n" }, { "name": "copy", "content": "Type: quadoption\nDefault: yes\n\nThis variable controls whether or not copies of your outgoing messages will be saved\nfor later references. Also see $record, $savename, $forcename and “fcc-hook”.\n\n\n\ncopydecodeweed\nType: boolean\nDefault: no\n\nControls whether Mutt will weed headers when invoking the or functions.\n\n\n\ncountalternatives\nType: boolean\nDefault: no\n\nWhen set, Mutt will recurse inside multipart/alternatives while performing attachment\nsearching and counting (see attachments).\n\nTraditionally, multipart/alternative parts have simply represented different encodings\nof the main content of the email. Unfortunately, some mail clients have started to\nplace email attachments inside one of alternatives. Setting this will allow Mutt to\nfind and count matching attachments hidden there, and include them in the index via %X\nor through ~X pattern matching.\n\n\n\ncursoroverlay\nType: boolean\nDefault: no\n\nWhen set, Mutt will overlay the indicator, tree, sidebarhighlight, and sidebarindi‐\ncator colors onto the currently selected line. This will allow default colors in\nthose to be overridden, and for attributes to be merged between the layers.\n\n\n\ncryptautoencrypt\nType: boolean\nDefault: no\n\nSetting this variable will cause Mutt to always attempt to PGP encrypt outgoing mes‐\nsages. This is probably only useful in connection to the “send-hook” command. It can\nbe overridden by use of the pgp menu, when encryption is not required or signing is\nrequested as well. If $smimeisdefault is set, then OpenSSL is used instead to cre‐\nate S/MIME messages and settings can be overridden by use of the smime menu instead.\n(Crypto only)\n\n\n\ncryptautopgp\nType: boolean\nDefault: yes\n\nThis variable controls whether or not mutt may automatically enable PGP encryp‐\ntion/signing for messages. See also $cryptautoencrypt, $cryptreplyencrypt,\n$cryptautosign, $cryptreplysign and $smimeisdefault.\n\n\n\ncryptautosign\nType: boolean\nDefault: no\n\nSetting this variable will cause Mutt to always attempt to cryptographically sign out‐\ngoing messages. This can be overridden by use of the pgp menu, when signing is not\nrequired or encryption is requested as well. If $smimeisdefault is set, then OpenSSL\nis used instead to create S/MIME messages and settings can be overridden by use of the\nsmime menu instead of the pgp menu. (Crypto only)\n\n\n\ncryptautosmime\nType: boolean\nDefault: yes\n\nThis variable controls whether or not mutt may automatically enable S/MIME encryp‐\ntion/signing for messages. See also $cryptautoencrypt, $cryptreplyencrypt,\n$cryptautosign, $cryptreplysign and $smimeisdefault.\n\n\n\ncryptconfirmhook\nType: boolean\nDefault: yes\n\nIf set, then you will be prompted for confirmation of keys when using the crypt-hook\ncommand. If unset, no such confirmation prompt will be presented. This is generally\nconsidered unsafe, especially where typos are concerned.\n\n\n\ncryptopportunisticencrypt\nType: boolean\nDefault: no\n\nSetting this variable will cause Mutt to automatically enable and disable encryption,\nbased on whether all message recipient keys can be located by Mutt.\n\nWhen this option is enabled, Mutt will enable/disable encryption each time the TO, CC,\nand BCC lists are edited. If $editheaders is set, Mutt will also do so each time the\nmessage is edited.\n\nWhile this is set, encryption can't be manually enabled/disabled. The pgp or smime\nmenus provide a selection to temporarily disable this option for the current message.\n\nIf $cryptautoencrypt or $cryptreplyencrypt enable encryption for a message, this op‐\ntion will be disabled for that message. It can be manually re-enabled in the pgp or\nsmime menus. (Crypto only)\n\n\n\ncryptopportunisticencryptstrongkeys\nType: boolean\nDefault: no\n\nWhen set, this modifies the behavior of $cryptopportunisticencrypt to only search\nfor ”strong keys”, that is, keys with full validity according to the web-of-trust al‐\ngorithm. A key with marginal or no validity will not enable opportunistic encryption.\n\nFor S/MIME, the behavior depends on the backend. Classic S/MIME will filter for cer‐\ntificates with the 't' (trusted) flag in the .index file. The GPGME backend will use\nthe same filters as with OpenPGP, and depends on GPGME's logic for assigning the\nGPGMEVALIDITYFULL and GPGMEVALIDITYULTIMATE validity flag.\n\n\n\ncryptprotectedheadersread\nType: boolean\nDefault: yes\n\nWhen set, Mutt will display protected headers in the pager, and will update the index\nand header cache with revised headers. Protected headers are stored inside the en‐\ncrypted or signed part of an an email, to prevent disclosure or tampering. For more\ninformation see https://github.com/autocrypt/protected-headers. Currently Mutt only\nsupports the Subject header.\n\nEncrypted messages using protected headers often substitute the exposed Subject header\nwith a dummy value (see $cryptprotectedheaderssubject). Mutt will update its con‐\ncept of the correct subject after the message is opened, i.e. via the function. If you reply to a message before opening it, Mutt will end up using\nthe dummy Subject header, so be sure to open such a message first. (Crypto only)\n\n\n\ncryptprotectedheaderssave\nType: boolean\nDefault: no\n\nWhen $cryptprotectedheadersread is set, and a message with a protected Subject is\nopened, Mutt will save the updated Subject into the header cache by default. This al‐\nlows searching/limiting based on the protected Subject header if the mailbox is\nre-opened, without having to re-open the message each time. However, for mbox/mh\nmailbox types, or if header caching is not set up, you would need to re-open the mes‐\nsage each time the mailbox was reopened before you could see or search/limit on the\nprotected subject again.\n\nWhen this variable is set, Mutt additionally saves the protected Subject back in the\nclear-text message headers. This provides better usability, but with the tradeoff of\nreduced security. The protected Subject header, which may have previously been en‐\ncrypted, is now stored in clear-text in the message headers. Copying the message\nelsewhere, via Mutt or external tools, could expose this previously encrypted data.\nPlease make sure you understand the consequences of this before you enable this vari‐\nable. (Crypto only)\n\n\n\ncryptprotectedheaderssubject\nType: string\nDefault: “...”\n\nWhen $cryptprotectedheaderswrite is set, and the message is marked for encryption,\nthis will be substituted into the Subject field in the message headers. To prevent a\nsubject from being substituted, unset this variable, or set it to the empty string.\n(Crypto only)\n\n\n\ncryptprotectedheaderswrite\nType: boolean\nDefault: no\n\nWhen set, Mutt will generate protected headers for signed and encrypted emails. Pro‐\ntected headers are stored inside the encrypted or signed part of an an email, to pre‐\nvent disclosure or tampering. For more information see https://github.com/au‐\ntocrypt/protected-headers. Currently Mutt only supports the Subject header. (Crypto\nonly)\n\n\n\ncryptreplyencrypt\nType: boolean\nDefault: yes\n\nIf set, automatically PGP or OpenSSL encrypt replies to messages which are encrypted.\n(Crypto only)\n\n\n\ncryptreplysign\nType: boolean\nDefault: no\n\nIf set, automatically PGP or OpenSSL sign replies to messages which are signed.\n\nNote: this does not work on messages that are encrypted and signed! (Crypto only)\n\n\n\ncryptreplysignencrypted\nType: boolean\nDefault: no\n\nIf set, automatically PGP or OpenSSL sign replies to messages which are encrypted.\nThis makes sense in combination with $cryptreplyencrypt, because it allows you to\nsign all messages which are automatically encrypted. This works around the problem\nnoted in $cryptreplysign, that mutt is not able to find out whether an encrypted mes‐\nsage is also signed. (Crypto only)\n\n\n\ncrypttimestamp\nType: boolean\nDefault: yes\n\nIf set, mutt will include a time stamp in the lines surrounding PGP or S/MIME output,\nso spoofing such lines is more difficult. If you are using colors to mark these\nlines, and rely on these, you may unset this setting. (Crypto only)\n\n\n\ncryptusegpgme\nType: boolean\nDefault: no\n\nThis variable controls the use of the GPGME-enabled crypto backends. If it is set and\nMutt was built with gpgme support, the gpgme code for S/MIME and PGP will be used in‐\nstead of the classic code. Note that you need to set this option in .muttrc; it won't\nhave any effect when used interactively.\n\nNote that the GPGME backend does not support creating old-style inline (traditional)\nPGP encrypted or signed messages (see $pgpautoinline).\n\n\n\ncryptusepka\nType: boolean\nDefault: no\n\nControls whether mutt uses PKA (see http://www.g10code.de/docs/pka-intro.de.pdf) dur‐\ning signature verification (only supported by the GPGME backend).\n\n\n\ncryptverifysig\nType: quadoption\nDefault: yes\n\nIf “yes”, always attempt to verify PGP or S/MIME signatures. If “ask-*”, ask whether\nor not to verify the signature. If “no”, never attempt to verify cryptographic signa‐\ntures. (Crypto only)\n\n\n\ndateformat\nType: string\nDefault: “!%a, %b %d, %Y at %I:%M:%S%p %Z”\n\nThis variable controls the format of the date printed by the “%d” sequence in $in‐\ndexformat. This is passed to the strftime(3) function to process the date, see the\nman page for the proper syntax.\n\nUnless the first character in the string is a bang (“!”), the month and week day names\nare expanded according to the locale. If the first character in the string is a bang,\nthe bang is discarded, and the month and week day names in the rest of the string are\nexpanded in the C locale (that is in US English).\n\n\n\ndefaulthook\nType: string\nDefault: “~f %s !~P | (~P ~C %s)”\n\nThis variable controls how “message-hook”, “reply-hook”, “send-hook”, “send2-hook”,\n“save-hook”, and “fcc-hook” will be interpreted if they are specified with only a sim‐\nple regexp, instead of a matching pattern. The hooks are expanded when they are de‐\nclared, so a hook will be interpreted according to the value of this variable at the\ntime the hook is declared.\n\nThe default value matches if the message is either from a user matching the regular\nexpression given, or if it is from you (if the from address matches “alternates”) and\nis to or cc'ed to a user matching the given regular expression.\n\n\n" }, { "name": "delete", "content": "Type: quadoption\nDefault: ask-yes\n\nControls whether or not messages are really deleted when closing or synchronizing a\nmailbox. If set to yes, messages marked for deleting will automatically be purged\nwithout prompting. If set to no, messages marked for deletion will be kept in the\nmailbox.\n\n\n\ndeleteuntag\nType: boolean\nDefault: yes\n\nIf this option is set, mutt will untag messages when marking them for deletion. This\napplies when you either explicitly delete a message, or when you save it to another\nfolder.\n\n\n\ndigestcollapse\nType: boolean\nDefault: yes\n\nIf this option is set, mutt's received-attachments menu will not show the subparts of\nindividual messages in a multipart/digest. To see these subparts, press “v” on that\nmenu.\n\n\n\ndisplayfilter\nType: path\nDefault: “”\n\nWhen set, specifies a command used to filter messages. When a message is viewed it is\npassed as standard input to $displayfilter, and the filtered message is read from the\nstandard output.\n\n\n\ndotlockprogram\nType: path\nDefault: “/usr/bin/muttdotlock”\n\nContains the path of the muttdotlock(1) binary to be used by mutt.\n\n\n\ndsnnotify\nType: string\nDefault: “”\n\nThis variable sets the request for when notification is returned. The string consists\nof a comma separated list (no spaces!) of one or more of the following: never, to\nnever request notification, failure, to request notification on transmission failure,\ndelay, to be notified of message delays, success, to be notified of successful trans‐\nmission.\n\nExample:\n\n\nset dsnnotify=”failure,delay”\n\n\nNote: when using $sendmail for delivery, you should not enable this unless you are ei‐\nther using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)-compatible in‐\nterface supporting the -N option for DSN. For SMTP delivery, DSN support is auto-de‐\ntected so that it depends on the server whether DSN will be used or not.\n\n\n\ndsnreturn\nType: string\nDefault: “”\n\nThis variable controls how much of your message is returned in DSN messages. It may\nbe set to either hdrs to return just the message header, or full to return the full\nmessage.\n\nExample:\n\n\nset dsnreturn=hdrs\n\n\nNote: when using $sendmail for delivery, you should not enable this unless you are ei‐\nther using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)-compatible in‐\nterface supporting the -R option for DSN. For SMTP delivery, DSN support is auto-de‐\ntected so that it depends on the server whether DSN will be used or not.\n\n\n\nduplicatethreads\nType: boolean\nDefault: yes\n\nThis variable controls whether mutt, when $sort is set to threads, threads messages\nwith the same Message-Id together. If it is set, it will indicate that it thinks they\nare duplicates of each other with an equals sign in the thread tree.\n\n\n\neditheaders\nType: boolean\nDefault: no\n\nThis option allows you to edit the header of your outgoing messages along with the\nbody of your message.\n\nAlthough the compose menu may have localized header labels, the labels passed to your\neditor will be standard RFC 2822 headers, (e.g. To:, Cc:, Subject:). Headers added in\nyour editor must also be RFC 2822 headers, or one of the pseudo headers listed in\n“edit-header”. Mutt will not understand localized header labels, just as it would not\nwhen parsing an actual email.\n\nNote that changes made to the References: and Date: headers are ignored for interoper‐\nability reasons.\n\n\n" }, { "name": "editor", "content": "Type: path\nDefault: “”\n\nThis variable specifies which editor is used by mutt. It defaults to the value of the\n$VISUAL, or $EDITOR, environment variable, or to the string “vi” if neither of those\nare set.\n\nThe $editor string may contain a %s escape, which will be replaced by the name of the\nfile to be edited. If the %s escape does not appear in $editor, a space and the name\nto be edited are appended.\n\nThe resulting string is then executed by running\n\n\nsh -c 'string'\n\n\nwhere string is the expansion of $editor described above.\n\n\n\nencodefrom\nType: boolean\nDefault: no\n\nWhen set, mutt will quoted-printable encode messages when they contain the string\n“From ” (note the trailing space) in the beginning of a line. This is useful to avoid\nthe tampering certain mail delivery and transport agents tend to do with messages (in\norder to prevent tools from misinterpreting the line as a mbox message separator).\n\n\n\nentropyfile\nType: path\nDefault: “”\n\nThe file which includes random data that is used to initialize SSL library functions.\n\n\n\nenvelopefromaddress\nType: e-mail address\nDefault: “”\n\nManually sets the envelope sender for outgoing messages. This value is ignored if\n$useenvelopefrom is unset.\n\n\n\nerrorhistory\nType: number\nDefault: 30\n\nThis variable controls the size (in number of strings remembered) of the error mes‐\nsages displayed by mutt. These can be shown with the function. The\nhistory is cleared each time this variable is set.\n\n\n" }, { "name": "escape", "content": "Type: string\nDefault: “~”\n\nEscape character to use for functions in the built-in editor.\n\n\n\nfastreply\nType: boolean\nDefault: no\n\nWhen set, the initial prompt for recipients and subject are skipped when replying to\nmessages, and the initial prompt for subject is skipped when forwarding messages.\n\nNote: this variable has no effect when the $autoedit variable is set.\n\n\n\nfccattach\nType: quadoption\nDefault: yes\n\nThis variable controls whether or not attachments on outgoing messages are saved along\nwith the main body of your message.\n\nNote: $fccbeforesend forces the default (set) behavior of this option.\n\n\n\nfccbeforesend\nType: boolean\nDefault: no\n\nWhen this variable is set, FCCs will occur before sending the message. Before send‐\ning, the message cannot be manipulated, so it will be stored the exact same as sent:\n$fccattach and $fccclear will be ignored (using their default values).\n\nWhen unset, the default, FCCs will occur after sending. Variables $fccattach and\n$fccclear will be respected, allowing it to be stored without attachments or encryp‐\ntion/signing if desired.\n\n\n\nfccclear\nType: boolean\nDefault: no\n\nWhen this variable is set, FCCs will be stored unencrypted and unsigned, even when the\nactual message is encrypted and/or signed.\n\nNote: $fccbeforesend forces the default (unset) behavior of this option. (PGP only)\n\nSee also $pgpselfencrypt, $smimeselfencrypt.\n\n\n\nfccdelimiter\nType: string\nDefault: “”\n\nWhen specified, this allows the ability to Fcc to more than one mailbox. The fcc\nvalue will be split by this delimiter and Mutt will evaluate each part as a mailbox\nseparately.\n\nSee $record, “fcc-hook”, and “fcc-save-hook”.\n\n\n\nflagsafe\nType: boolean\nDefault: no\n\nIf set, flagged messages cannot be deleted.\n\n\n" }, { "name": "folder", "content": "Type: path\nDefault: “~/Mail”\n\nSpecifies the default location of your mailboxes. A “+” or “=” at the beginning of a\npathname will be expanded to the value of this variable. Note that if you change this\nvariable (from the default) value you need to make sure that the assignment occurs be‐\nfore you use “+” or “=” for any other variables since expansion takes place when han‐\ndling the “mailboxes” command.\n\n\n\nfolderformat\nType: string\nDefault: “%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f”\n\nThis variable allows you to customize the file browser display to your personal taste.\nThis string is similar to $indexformat, but has its own set of printf(3)-like se‐\nquences:\n%C current file number\n%d date/time folder was last modified\n%D date/time folder was last modified using $dateformat.\n%f filename (“/” is appended to directory names, “@” to symbolic links and “*” to\nexecutable files)\n%F file permissions\n%g group name (or numeric gid, if missing)\n%l number of hard links\n%m number of messages in the mailbox *\n%n number of unread messages in the mailbox *\n%N N if mailbox has new mail, blank otherwise\n%s size in bytes (see formatstrings-size)\n%t “*” if the file is tagged, blank otherwise\n%u owner name (or numeric uid, if missing)\n%>X right justify the rest of the string and pad with character “X”\n%|X pad to the end of the line with character “X”\n%*X soft-fill with character “X” as pad\n\nFor an explanation of “soft-fill”, see the $indexformat documentation.\n\n* = can be optionally printed if nonzero\n\n%m, %n, and %N only work for monitored mailboxes. %m requires $mailcheckstats to be\nset. %n requires $mailcheckstats to be set (except for IMAP mailboxes).\n\n\n\nfollowupto\nType: boolean\nDefault: yes\n\nControls whether or not the “Mail-Followup-To:” header field is generated when sending\nmail. When set, Mutt will generate this field when you are replying to a known mail‐\ning list, specified with the “subscribe” or “lists” commands.\n\nThis field has two purposes. First, preventing you from receiving duplicate copies of\nreplies to messages which you send to mailing lists, and second, ensuring that you do\nget a reply separately for any messages sent to known lists to which you are not sub‐\nscribed.\n\nThe header will contain only the list's address for subscribed lists, and both the\nlist address and your own email address for unsubscribed lists. Without this header,\na group reply to your message sent to a subscribed list will be sent to both the list\nand your address, resulting in two copies of the same email for you.\n\n\n\nforcename\nType: boolean\nDefault: no\n\nThis variable is similar to $savename, except that Mutt will store a copy of your\noutgoing message by the username of the address you are sending to even if that mail‐\nbox does not exist.\n\nAlso see the $record variable.\n\n\n\nforwardattachments\nType: quadoption\nDefault: ask-yes\n\nWhen forwarding inline (i.e. $mimeforward unset or answered with “no” and $for‐\nwarddecode set), attachments which cannot be decoded in a reasonable manner will be\nattached to the newly composed message if this quadoption is set or answered with\n“yes”.\n\n\n\nforwardattributionintro\nType: string (localized)\nDefault: “----- Forwarded message from %f -----”\n\nThis is the string that will precede a message which has been forwarded in the main\nbody of a message (when $mimeforward is unset). For a full listing of defined\nprintf(3)-like sequences see the section on $indexformat. See also $attributionlo‐\ncale.\n\n\n\nforwardattributiontrailer\nType: string (localized)\nDefault: “----- End forwarded message -----”\n\nThis is the string that will follow a message which has been forwarded in the main\nbody of a message (when $mimeforward is unset). For a full listing of defined\nprintf(3)-like sequences see the section on $indexformat. See also $attributionlo‐\ncale.\n\n\n\nforwarddecode\nType: boolean\nDefault: yes\n\nControls the decoding of complex MIME messages into text/plain when forwarding a mes‐\nsage. The message header is also RFC2047 decoded. This variable is only used, if\n$mimeforward is unset, otherwise $mimeforwarddecode is used instead.\n\n\n\nforwarddecrypt\nType: quadoption\nDefault: yes\n\nThis quadoption controls the handling of encrypted messages when forwarding or attach‐\ning a message. When set to or answered “yes”, the outer layer of encryption is\nstripped off.\n\nThis variable is used if $mimeforward is set and $mimeforwarddecode is unset. It\nis also used when attaching a message via in the compose menu. (PGP\nonly)\n\n\n\nforwardedit\nType: quadoption\nDefault: yes\n\nThis quadoption controls whether or not the user is automatically placed in the editor\nwhen forwarding messages. For those who always want to forward with no modification,\nuse a setting of “no”.\n\n\n\nforwardformat\nType: string\nDefault: “[%a: %s]”\n\nThis variable controls the default subject when forwarding a message. It uses the\nsame format sequences as the $indexformat variable.\n\n\n\nforwardquote\nType: boolean\nDefault: no\n\nWhen set, forwarded messages included in the main body of the message (when $mimefor‐\nward is unset) will be quoted using $indentstring.\n\n\n" }, { "name": "from", "content": "Type: e-mail address\nDefault: “”\n\nWhen set, this variable contains a default from address. It can be overridden using\n“myhdr” (including from a “send-hook”) and $reversename. This variable is ignored\nif $usefrom is unset.\n\nThis setting defaults to the contents of the environment variable $EMAIL.\n\n\n\ngecosmask\nType: regular expression\nDefault: “^[^,]*”\n\nA regular expression used by mutt to parse the GECOS field of a password entry when\nexpanding the alias. The default value will return the string up to the first “,” en‐\ncountered. If the GECOS field contains a string like “lastname, firstname” then you\nshould set it to “.*”.\n\nThis can be useful if you see the following behavior: you address an e-mail to user ID\n“stevef” whose full name is “Steve Franklin”. If mutt expands “stevef” to “”Franklin”\nstevef@foo.bar” then you should set the $gecosmask to a regular expression that will\nmatch the whole name so mutt will expand “Franklin” to “Franklin, Steve”.\n\n\n" }, { "name": "hdrs", "content": "Type: boolean\nDefault: yes\n\nWhen unset, the header fields normally added by the “myhdr” command are not created.\nThis variable must be unset before composing a new message or replying in order to\ntake effect. If set, the user defined header fields are added to every new message.\n\n\n" }, { "name": "header", "content": "Type: boolean\nDefault: no\n\nWhen set, this variable causes Mutt to include the header of the message you are re‐\nplying to into the edit buffer. The $weed setting applies.\n\n\n\nheadercache\nType: path\nDefault: “”\n\nThis variable points to the header cache database. If pointing to a directory Mutt\nwill contain a header cache database file per folder, if pointing to a file that file\nwill be a single global header cache. By default it is unset so no header caching will\nbe used.\n\nHeader caching can greatly improve speed when opening POP, IMAP MH or Maildir folders,\nsee “caching” for details.\n\n\n\nheadercachecompress\nType: boolean\nDefault: yes\n\nWhen mutt is compiled with qdbm, tokyocabinet, or kyotocabinet as header cache back‐\nend, this option determines whether the database will be compressed. Compression re‐\nsults in database files roughly being one fifth of the usual diskspace, but the decom‐\npression can result in a slower opening of cached folder(s) which in general is still\nmuch faster than opening non header cached folders.\n\n\n\nheadercachepagesize\nType: number (long)\nDefault: 16384\n\nWhen mutt is compiled with either gdbm or bdb4 as the header cache backend, this op‐\ntion changes the database page size. Too large or too small values can waste space,\nmemory, or CPU time. The default should be more or less optimal for most use cases.\n\n\n\nheadercolorpartial\nType: boolean\nDefault: no\n\nWhen set, color header regexps behave like color body regexps: color is applied to the\nexact text matched by the regexp. When unset, color is applied to the entire header.\n\nOne use of this option might be to apply color to just the header labels.\n\nSee “color” for more details.\n\n\n" }, { "name": "help", "content": "Type: boolean\nDefault: yes\n\nWhen set, help lines describing the bindings for the major functions provided by each\nmenu are displayed on the first line of the screen.\n\nNote: The binding will not be displayed correctly if the function is bound to a se‐\nquence rather than a single keystroke. Also, the help line may not be updated if a\nbinding is changed while Mutt is running. Since this variable is primarily aimed at\nnew users, neither of these should present a major problem.\n\n\n\nhiddenhost\nType: boolean\nDefault: no\n\nWhen set, mutt will skip the host name part of $hostname variable when adding the do‐\nmain part to addresses. This variable does not affect the generation of Message-IDs,\nand it will not lead to the cut-off of first-level domains.\n\n\n\nhidelimited\nType: boolean\nDefault: no\n\nWhen set, mutt will not show the presence of messages that are hidden by limiting, in\nthe thread tree.\n\n\n\nhidemissing\nType: boolean\nDefault: yes\n\nWhen set, mutt will not show the presence of missing messages in the thread tree.\n\n\n\nhidethreadsubject\nType: boolean\nDefault: yes\n\nWhen set, mutt will not show the subject of messages in the thread tree that have the\nsame subject as their parent or closest previously displayed sibling.\n\n\n\nhidetoplimited\nType: boolean\nDefault: no\n\nWhen set, mutt will not show the presence of messages that are hidden by limiting, at\nthe top of threads in the thread tree. Note that when $hidelimited is set, this op‐\ntion will have no effect.\n\n\n\nhidetopmissing\nType: boolean\nDefault: yes\n\nWhen set, mutt will not show the presence of missing messages at the top of threads in\nthe thread tree. Note that when $hidemissing is set, this option will have no ef‐\nfect.\n\n\n" }, { "name": "history", "content": "Type: number\nDefault: 10\n\nThis variable controls the size (in number of strings remembered) of the string his‐\ntory buffer per category. The buffer is cleared each time the variable is set.\n\n\n\nhistoryfile\nType: path\nDefault: “~/.mutthistory”\n\nThe file in which Mutt will save its history.\n\nAlso see $savehistory.\n\n\n\nhistoryremovedups\nType: boolean\nDefault: no\n\nWhen set, all of the string history will be scanned for duplicates when a new entry is\nadded. Duplicate entries in the $historyfile will also be removed when it is period‐\nically compacted.\n\n\n\nhonordisposition\nType: boolean\nDefault: no\n\nWhen set, Mutt will not display attachments with a disposition of “attachment” inline\neven if it could render the part to plain text. These MIME parts can only be viewed\nfrom the attachment menu.\n\nIf unset, Mutt will render all MIME parts it can properly transform to plain text.\n\n\n\nhonorfollowupto\nType: quadoption\nDefault: yes\n\nThis variable controls whether or not a Mail-Followup-To header is honored when\ngroup-replying to a message.\n\n\n" }, { "name": "hostname", "content": "Type: string\nDefault: “”\n\nSpecifies the fully-qualified hostname of the system mutt is running on containing the\nhost's name and the DNS domain it belongs to. It is used as the domain part (after\n“@”) for local email addresses as well as Message-Id headers.\n\nIts value is determined at startup as follows: the node's hostname is first determined\nby the uname(3) function. The domain is then looked up using the gethostname(2) and\ngetaddrinfo(3) functions. If those calls are unable to determine the domain, the full\nvalue returned by uname is used. Optionally, Mutt can be compiled with a fixed domain\nname in which case a detected one is not used.\n\nStarting in Mutt 2.0, the operations described in the previous paragraph are performed\nafter the muttrc is processed, instead of beforehand. This way, if the DNS operations\nare creating delays at startup, you can avoid those by manually setting the value in\nyour muttrc.\n\nAlso see $usedomain and $hiddenhost.\n\n\n\nidndecode\nType: boolean\nDefault: yes\n\nWhen set, Mutt will show you international domain names decoded. Note: You can use\nIDNs for addresses even if this is unset. This variable only affects decoding. (IDN\nonly)\n\n\n\nidnencode\nType: boolean\nDefault: yes\n\nWhen set, Mutt will encode international domain names using IDN. Unset this if your\nSMTP server can handle newer (RFC 6531) UTF-8 encoded domains. (IDN only)\n\n\n\nignorelinearwhitespace\nType: boolean\nDefault: no\n\nThis option replaces linear-white-space between encoded-word and text to a single\nspace to prevent the display of MIME-encoded “Subject:” field from being divided into\nmultiple lines.\n\n\n\nignorelistreplyto\nType: boolean\nDefault: no\n\nAffects the behavior of the function when replying to messages from mailing\nlists (as defined by the “subscribe” or “lists” commands). When set, if the “Re‐\nply-To:” field is set to the same value as the “To:” field, Mutt assumes that the “Re‐\nply-To:” field was set by the mailing list to automate responses to the list, and will\nignore this field. To direct a response to the mailing list when this option is set,\nuse the function; will reply to both the sender and the\nlist.\n\n\n\nimapauthenticators\nType: string\nDefault: “”\n\nThis is a colon-delimited list of authentication methods mutt may attempt to use to\nlog in to an IMAP server, in the order mutt should try them. Authentication methods\nare either “login” or the right side of an IMAP “AUTH=xxx” capability string, e.g.\n“digest-md5”, “gssapi” or “cram-md5”. This option is case-insensitive. If it's unset\n(the default) mutt will try all available methods, in order from most-secure to\nleast-secure.\n\nExample:\n\n\nset imapauthenticators=”gssapi:cram-md5:login”\n\n\nNote: Mutt will only fall back to other authentication methods if the previous methods\nare unavailable. If a method is available but authentication fails, mutt will not con‐\nnect to the IMAP server.\n\n\n\nimapchecksubscribed\nType: boolean\nDefault: no\n\nWhen set, mutt will fetch the set of subscribed folders from your server on connec‐\ntion, and add them to the set of mailboxes it polls for new mail just as if you had\nissued individual “mailboxes” commands.\n\n\n\nimapcondstore\nType: boolean\nDefault: no\n\nWhen set, mutt will use the CONDSTORE extension (RFC 7162) if advertised by the\nserver. Mutt's current implementation is basic, used only for initial message fetch‐\ning and flag updates.\n\nFor some IMAP servers, enabling this will slightly speed up downloading initial mes‐\nsages. Unfortunately, Gmail is not one those, and displays worse performance when en‐\nabled. Your mileage may vary.\n\n\n\nimapdeflate\nType: boolean\nDefault: no\n\nWhen set, mutt will use the COMPRESS=DEFLATE extension (RFC 4978) if advertised by the\nserver.\n\nIn general a good compression efficiency can be achieved, which speeds up reading\nlarge mailboxes also on fairly good connections.\n\n\n\nimapdelimchars\nType: string\nDefault: “/.”\n\nThis contains the list of characters which you would like to treat as folder separa‐\ntors for displaying IMAP paths. In particular it helps in using the “=” shortcut for\nyour folder variable.\n\n\n\nimapfetchchunksize\nType: number (long)\nDefault: 0\n\nWhen set to a value greater than 0, new headers will be downloaded in groups of this\nmany headers per request. If you have a very large mailbox, this might prevent a\ntimeout and disconnect when opening the mailbox, by sending a FETCH per set of this\nmany headers, instead of a single FETCH for all new headers.\n\n\n\nimapheaders\nType: string\nDefault: “”\n\nMutt requests these header fields in addition to the default headers (“Date:”,\n“From:”, “Sender:”, “Subject:”, “To:”, “Cc:”, “Message-Id:”, “References:”, “Con‐\ntent-Type:”, “Content-Description:”, “In-Reply-To:”, “Reply-To:”, “Lines:”,\n“List-Post:”, “X-Label:”) from IMAP servers before displaying the index menu. You may\nwant to add more headers for spam detection.\n\nNote: This is a space separated list, items should be uppercase and not contain the\ncolon, e.g. “X-BOGOSITY X-SPAM-STATUS” for the “X-Bogosity:” and “X-Spam-Status:”\nheader fields.\n\n\n\nimapidle\nType: boolean\nDefault: no\n\nWhen set, mutt will attempt to use the IMAP IDLE extension to check for new mail in\nthe current mailbox. Some servers (dovecot was the inspiration for this option) react\nbadly to mutt's implementation. If your connection seems to freeze up periodically,\ntry unsetting this.\n\n\n\nimapkeepalive\nType: number\nDefault: 300\n\nThis variable specifies the maximum amount of time in seconds that mutt will wait be‐\nfore polling open IMAP connections, to prevent the server from closing them before\nmutt has finished with them. The default is well within the RFC-specified minimum\namount of time (30 minutes) before a server is allowed to do this, but in practice the\nRFC does get violated every now and then. Reduce this number if you find yourself get‐\nting disconnected from your IMAP server due to inactivity.\n\n\n\nimaplistsubscribed\nType: boolean\nDefault: no\n\nThis variable configures whether IMAP folder browsing will look for only subscribed\nfolders or all folders. This can be toggled in the IMAP browser with the function.\n\n\n\nimaplogin\nType: string\nDefault: “”\n\nYour login name on the IMAP server.\n\nThis variable defaults to the value of $imapuser.\n\n\n\nimapoauthrefreshcommand\nType: string\nDefault: “”\n\nThe command to run to generate an OAUTH refresh token for authorizing your connection\nto your IMAP server. This command will be run on every connection attempt that uses\nthe OAUTHBEARER authentication mechanism. See “oauth” for details.\n\n\n\nimappass\nType: string\nDefault: “”\n\nSpecifies the password for your IMAP account. If unset, Mutt will prompt you for your\npassword when you invoke the function or try to open an IMAP folder.\n\nWarning: you should only use this option when you are on a fairly secure machine, be‐\ncause the superuser can read your muttrc even if you are the only one who can read the\nfile.\n\n\n\nimappassive\nType: boolean\nDefault: yes\n\nWhen set, mutt will not open new IMAP connections to check for new mail. Mutt will\nonly check for new mail over existing IMAP connections. This is useful if you don't\nwant to be prompted for user/password pairs on mutt invocation, or if opening the con‐\nnection is slow.\n\n\n\nimappeek\nType: boolean\nDefault: yes\n\nWhen set, mutt will avoid implicitly marking your mail as read whenever you fetch a\nmessage from the server. This is generally a good thing, but can make closing an IMAP\nfolder somewhat slower. This option exists to appease speed freaks.\n\n\n\nimappipelinedepth\nType: number\nDefault: 15\n\nControls the number of IMAP commands that may be queued up before they are sent to the\nserver. A deeper pipeline reduces the amount of time mutt must wait for the server,\nand can make IMAP servers feel much more responsive. But not all servers correctly\nhandle pipelined commands, so if you have problems you might want to try setting this\nvariable to 0.\n\nNote: Changes to this variable have no effect on open connections.\n\n\n\nimappolltimeout\nType: number\nDefault: 15\n\nThis variable specifies the maximum amount of time in seconds that mutt will wait for\na response when polling IMAP connections for new mail, before timing out and closing\nthe connection. Set to 0 to disable timing out.\n\n\n\nimapqresync\nType: boolean\nDefault: no\n\nWhen set, mutt will use the QRESYNC extension (RFC 7162) if advertised by the server.\nMutt's current implementation is basic, used only for initial message fetching and\nflag updates.\n\nNote: this feature is currently experimental. If you experience strange behavior,\nsuch as duplicate or missing messages please file a bug report to let us know.\n\n\n\nimapservernoise\nType: boolean\nDefault: yes\n\nWhen set, mutt will display warning messages from the IMAP server as error messages.\nSince these messages are often harmless, or generated due to configuration problems on\nthe server which are out of the users' hands, you may wish to suppress them at some\npoint.\n\n\n\nimapuser\nType: string\nDefault: “”\n\nThe name of the user whose mail you intend to access on the IMAP server.\n\nThis variable defaults to your user name on the local machine.\n\n\n\nimplicitautoview\nType: boolean\nDefault: no\n\nIf set to “yes”, mutt will look for a mailcap entry with the “copiousoutput” flag set\nfor every MIME attachment it doesn't have an internal viewer defined for. If such an\nentry is found, mutt will use the viewer defined in that entry to convert the body\npart to text form.\n\n\n" }, { "name": "include", "content": "Type: quadoption\nDefault: ask-yes\n\nControls whether or not a copy of the message(s) you are replying to is included in\nyour reply.\n\n\n\nincludeencrypted\nType: boolean\nDefault: no\n\nControls whether or not Mutt includes separately encrypted attachment contents when\nreplying.\n\nThis variable was added to prevent accidental exposure of encrypted contents when re‐\nplying to an attacker. If a previously encrypted message were attached by the at‐\ntacker, they could trick an unwary recipient into decrypting and including the message\nin their reply.\n\n\n\nincludeonlyfirst\nType: boolean\nDefault: no\n\nControls whether or not Mutt includes only the first attachment of the message you are\nreplying.\n\n\n\nindentstring\nType: string\nDefault: “> ”\n\nSpecifies the string to prepend to each line of text quoted in a message to which you\nare replying. You are strongly encouraged not to change this value, as it tends to\nagitate the more fanatical netizens.\n\nThe value of this option is ignored if $textflowed is set, because the quoting mecha‐\nnism is strictly defined for format=flowed.\n\nThis option is a format string, please see the description of $indexformat for sup‐\nported printf(3)-style sequences.\n\n\n\nindexformat\nType: string\nDefault: “%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s”\n\nThis variable allows you to customize the message index display to your personal\ntaste.\n\n“Format strings” are similar to the strings used in the C function printf(3) to format\noutput (see the man page for more details). For an explanation of the %? construct,\nsee the $statusformat description. The following sequences are defined in Mutt:\n%a address of the author\n%A reply-to address (if present; otherwise: address of author)\n%b filename of the original message folder (think mailbox)\n%B the list to which the letter was sent, or else the folder name (%b).\n%c number of characters (bytes) in the message (see formatstrings-size)\n%C current message number\n%d date and time of the message in the format specified by $dateformat converted\nto sender's time zone\n%D date and time of the message in the format specified by $dateformat converted\nto the local time zone\n%e current message number in thread\n%E number of messages in current thread\n%f sender (address + real name), either From: or Return-Path:\n%F author name, or recipient name if the message is from you\n%H spam attribute(s) of this message\n%i message-id of the current message\n%l number of lines in the unprocessed message (may not work with maildir, mh, and\nIMAP folders)\n%L If an address in the “To:” or “Cc:” header field matches an address defined by\nthe users “subscribe” command, this displays ”To ”, otherwise the\nsame as %F.\n%m total number of message in the mailbox\n%M number of hidden messages if the thread is collapsed.\n%N message score\n%n author's real name (or address if missing)\n%O original save folder where mutt would formerly have stashed the message: list\nname or recipient name if not sent to a list\n%P progress indicator for the built-in pager (how much of the file has been dis‐\nplayed)\n%r comma separated list of “To:” recipients\n%R comma separated list of “Cc:” recipients\n%s subject of the message\n%S single character status of the message (“N”/“O”/“D”/“d”/“!”/“r”/“*”)\n%t “To:” field (recipients)\n%T the appropriate character from the $tochars string\n%u user (login) name of the author\n%v first name of the author, or the recipient if the message is from you\n%X number of attachments (please see the “attachments” section for possible speed\neffects)\n%y “X-Label:” field, if present\n%Y “X-Label:” field, if present, and (1) not at part of a thread tree, (2) at the\ntop of a thread, or (3) “X-Label:” is different from preceding message's “X-La‐\nbel:”.\n%Z a three character set of message status flags. the first character is\nnew/read/replied flags (“n”/“o”/“r”/“O”/“N”). the second is deleted or encryp‐\ntion flags (“D”/“d”/“S”/“P”/“s”/“K”). the third is either tagged/flagged\n(“*”/“!”), or one of the characters listed in $tochars.\n%@name@\ninsert and evaluate format-string from the matching “index-format-hook” command\n%{fmt} the date and time of the message is converted to sender's time zone, and “fmt”\nis expanded by the library function strftime(3); a leading bang disables lo‐\ncales\n%[fmt] the date and time of the message is converted to the local time zone, and “fmt”\nis expanded by the library function strftime(3); a leading bang disables lo‐\ncales\n%(fmt) the local date and time when the message was received. “fmt” is expanded by\nthe library function strftime(3); a leading bang disables locales\n% the current local time. “fmt” is expanded by the library function strftime(3);\na leading bang disables locales.\n%>X right justify the rest of the string and pad with character “X”\n%|X pad to the end of the line with character “X”\n%*X soft-fill with character “X” as pad\n\nNote that for mbox/mmdf, “%l” applies to the unprocessed message, and for maildir/mh,\nthe value comes from the “Lines:” header field when present (the meaning is normally\nthe same). Thus the value depends on the encodings used in the different parts of the\nmessage and has little meaning in practice.\n\n“Soft-fill” deserves some explanation: Normal right-justification will print every‐\nthing to the left of the “%>”, displaying padding and whatever lies to the right only\nif there's room. By contrast, soft-fill gives priority to the right-hand side, guaran‐\nteeing space to display it and showing padding only if there's still room. If neces‐\nsary, soft-fill will eat text leftwards to make room for rightward text.\n\nNote that these expandos are supported in “save-hook”, “fcc-hook”, “fcc-save-hook”,\nand “index-format-hook”.\n\nThey are also supported in the configuration variables $attribution, $forwardattribu‐\ntionintro, $forwardattributiontrailer, $forwardformat, $indentstring, $mes‐\nsageformat, $pagerformat, and $postindentstring.\n\n\n" }, { "name": "ispell", "content": "Type: path\nDefault: “/usr/bin/ispell”\n\nHow to invoke ispell (GNU's spell-checking software).\n\n\n\nkeepflagged\nType: boolean\nDefault: no\n\nIf set, read messages marked as flagged will not be moved from your spool mailbox to\nyour $mbox mailbox, or as a result of a “mbox-hook” command.\n\n\n\nlocaldateheader\nType: boolean\nDefault: yes\n\nIf set, convert the date in the Date header of sent emails into local (sender's) time‐\nzone.\n\n\n\nmailcheck\nType: number\nDefault: 5\n\nThis variable configures how often (in seconds) mutt should look for new mail. Also\nsee the $timeout variable.\n\n\n\nmailcheckrecent\nType: boolean\nDefault: yes\n\nWhen set, Mutt will only notify you about new mail that has been received since the\nlast time you opened the mailbox. When unset, Mutt will notify you if any new mail\nexists in the mailbox, regardless of whether you have visited it recently.\n\nWhen $markold is set, Mutt does not consider the mailbox to contain new mail if only\nold messages exist.\n\n\n\nmailcheckstats\nType: boolean\nDefault: no\n\nWhen set, mutt will periodically calculate message statistics of a mailbox while\npolling for new mail. It will check for unread, flagged, and total message counts.\nBecause this operation is more performance intensive, it defaults to unset, and has a\nseparate option, $mailcheckstatsinterval, to control how often to update these\ncounts.\n\nMessage statistics can also be explicitly calculated by invoking the \nfunction.\n\n\n\nmailcheckstatsinterval\nType: number\nDefault: 60\n\nWhen $mailcheckstats is set, this variable configures how often (in seconds) mutt\nwill update message counts.\n\n\n\nmailcappath\nType: string\nDefault: “”\n\nThis variable specifies which files to consult when attempting to display MIME bodies\nnot directly supported by Mutt. The default value is generated during startup: see\nthe “mailcap” section of the manual.\n\n\n\nmailcapsanitize\nType: boolean\nDefault: yes\n\nIf set, mutt will restrict possible characters in mailcap % expandos to a well-defined\nset of safe characters. This is the safe setting, but we are not sure it doesn't\nbreak some more advanced MIME stuff.\n\nDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE DOING!\n\n\n\nmaildirheadercacheverify\nType: boolean\nDefault: yes\n\nCheck for Maildir unaware programs other than mutt having modified maildir files when\nthe header cache is in use. This incurs one stat(2) per message every time the folder\nis opened (which can be very slow for NFS folders).\n\n\n\nmaildirtrash\nType: boolean\nDefault: no\n\nIf set, messages marked as deleted will be saved with the maildir trashed flag instead\nof unlinked. Note: this only applies to maildir-style mailboxes. Setting it will\nhave no effect on other mailbox types.\n\n\n\nmaildircheckcur\nType: boolean\nDefault: no\n\nIf set, mutt will poll both the new and cur directories of a maildir folder for new\nmessages. This might be useful if other programs interacting with the folder (e.g.\ndovecot) are moving new messages to the cur directory. Note that setting this option\nmay slow down polling for new messages in large folders, since mutt has to scan all\ncur messages.\n\n\n\nmarkmacroprefix\nType: string\nDefault: “'”\n\nPrefix for macros created using mark-message. A new macro automatically generated\nwith a will be composed from this prefix and the letter a.\n\n\n\nmarkold\nType: boolean\nDefault: yes\n\nControls whether or not mutt marks new unread messages as old if you exit a mailbox\nwithout reading them. With this option set, the next time you start mutt, the mes‐\nsages will show up with an “O” next to them in the index menu, indicating that they\nare old.\n\n\n" }, { "name": "markers", "content": "Type: boolean\nDefault: yes\n\nControls the display of wrapped lines in the internal pager. If set, a “+” marker is\ndisplayed at the beginning of wrapped lines.\n\nAlso see the $smartwrap variable.\n\n\n" }, { "name": "mask", "content": "Type: regular expression\nDefault: “!^\\.[^.]”\n\nA regular expression used in the file browser, optionally preceded by the not operator\n“!”. Only files whose names match this mask will be shown. The match is always\ncase-sensitive.\n\n\n" }, { "name": "mbox", "content": "Type: path\nDefault: “~/mbox”\n\nThis specifies the folder into which read mail in your $spoolfile folder will be ap‐\npended.\n\nAlso see the $move variable.\n\n\n\nmboxtype\nType: folder magic\nDefault: mbox\n\nThe default mailbox type used when creating new folders. May be any of “mbox”, “MMDF”,\n“MH” and “Maildir”. This is overridden by the -m command-line option.\n\n\n\nmenucontext\nType: number\nDefault: 0\n\nThis variable controls the number of lines of context that are given when scrolling\nthrough menus. (Similar to $pagercontext.)\n\n\n\nmenumoveoff\nType: boolean\nDefault: yes\n\nWhen unset, the bottom entry of menus will never scroll up past the bottom of the\nscreen, unless there are less entries than lines. When set, the bottom entry may move\noff the bottom.\n\n\n\nmenuscroll\nType: boolean\nDefault: no\n\nWhen set, menus will be scrolled up or down one line when you attempt to move across a\nscreen boundary. If unset, the screen is cleared and the next or previous page of the\nmenu is displayed (useful for slow links to avoid many redraws).\n\n\n\nmessagecacheclean\nType: boolean\nDefault: no\n\nIf set, mutt will clean out obsolete entries from the message cache when the mailbox\nis synchronized. You probably only want to set it every once in a while, since it can\nbe a little slow (especially for large folders).\n\n\n\nmessagecachedir\nType: path\nDefault: “”\n\nSet this to a directory and mutt will cache copies of messages from your IMAP and POP\nservers here. You are free to remove entries at any time.\n\nWhen setting this variable to a directory, mutt needs to fetch every remote message\nonly once and can perform regular expression searches as fast as for local folders.\n\nAlso see the $messagecacheclean variable.\n\n\n\nmessageformat\nType: string\nDefault: “%s”\n\nThis is the string displayed in the “attachment” menu for attachments of type mes‐‐\nsage/rfc822. For a full listing of defined printf(3)-like sequences see the section\non $indexformat.\n\n\n\nmessageidformat\nType: string\nDefault: “<%z@%f>”\n\nThis variable describes the format of the Message-ID generated when sending messages.\nMutt 2.0 introduced a more compact format, but this variable allows the ability to\nchoose your own format. The value may end in “|” to invoke an external filter. See\nformatstrings-filters.\n\nPlease note that the Message-ID value follows a strict syntax, and you are responsible\nfor ensuring correctness if you change this from the default. In particular, the\nvalue must follow the syntax in RFC 5322: “””<”” id-left ””@”” id-right ””>”””. No spaces\nare allowed, and id-left should follow the dot-atom-text syntax in the RFC. The\nid-right should generally be left at %f.\n\nThe old Message-ID format can be used by setting this to:\n“<%Y%02m%02d%02H%02M%02S.G%c%p@%f>”\n\nThe following printf(3)-style sequences are understood:\n%c step counter looping from “A” to “Z”\n%d current day of the month (GMT)\n%f $hostname\n%H current hour using a 24-hour clock (GMT)\n%m current month number (GMT)\n%M current minute of the hour (GMT)\n%p pid of the running mutt process\n%r 3 bytes of pseudorandom data encoded in Base64\n%S current second of the minute (GMT)\n%x 1 byte of pseudorandom data hex encoded (example: '1b')\n%Y current year using 4 digits (GMT)\n%z 4 byte timestamp + 8 bytes of pseudorandom data encoded in Base64\n\n\nmetakey\nType: boolean\nDefault: no\n\nIf set, forces Mutt to interpret keystrokes with the high bit (bit 8) set as if the\nuser had pressed the Esc key and whatever key remains after having the high bit re‐\nmoved. For example, if the key pressed has an ASCII value of 0xf8, then this is\ntreated as if the user had pressed Esc then “x”. This is because the result of remov‐\ning the high bit from 0xf8 is 0x78, which is the ASCII character “x”.\n\n\n" }, { "name": "metoo", "content": "Type: boolean\nDefault: no\n\nIf unset, Mutt will remove your address (see the “alternates” command) from the list\nof recipients when replying to a message.\n\n\n\nmhpurge\nType: boolean\nDefault: no\n\nWhen unset, mutt will mimic mh's behavior and rename deleted messages to , in mh folders instead of really deleting them. This leaves the message on disk\nbut makes programs reading the folder ignore it. If the variable is set, the message\nfiles will simply be deleted.\n\nThis option is similar to $maildirtrash for Maildir folders.\n\n\n\nmhseqflagged\nType: string\nDefault: “flagged”\n\nThe name of the MH sequence used for flagged messages.\n\n\n\nmhseqreplied\nType: string\nDefault: “replied”\n\nThe name of the MH sequence used to tag replied messages.\n\n\n\nmhsequnseen\nType: string\nDefault: “unseen”\n\nThe name of the MH sequence used for unseen messages.\n\n\n\nmimeforward\nType: quadoption\nDefault: no\n\nWhen set, the message you are forwarding will be attached as a separate message/rfc822\nMIME part instead of included in the main body of the message. This is useful for\nforwarding MIME messages so the receiver can properly view the message as it was de‐\nlivered to you. If you like to switch between MIME and not MIME from mail to mail, set\nthis variable to “ask-no” or “ask-yes”.\n\nAlso see $forwarddecode and $mimeforwarddecode.\n\n\n\nmimeforwarddecode\nType: boolean\nDefault: no\n\nControls the decoding of complex MIME messages into text/plain when forwarding a mes‐\nsage while $mimeforward is set. Otherwise $forwarddecode is used instead.\n\n\n\nmimeforwardrest\nType: quadoption\nDefault: yes\n\nWhen forwarding multiple attachments of a MIME message from the attachment menu, at‐\ntachments which cannot be decoded in a reasonable manner will be attached to the newly\ncomposed message if this option is set.\n\n\n\nmimetypequerycommand\nType: string\nDefault: “”\n\nThis specifies a command to run, to determine the mime type of a new attachment when\ncomposing a message. Unless $mimetypequeryfirst is set, this will only be run if\nthe attachment's extension is not found in the mime.types file.\n\nThe string may contain a “%s”, which will be substituted with the attachment filename.\nMutt will add quotes around the string substituted for “%s” automatically according to\nshell quoting rules, so you should avoid adding your own. If no “%s” is found in the\nstring, Mutt will append the attachment filename to the end of the string.\n\nThe command should output a single line containing the attachment's mime type.\n\nSuggested values are “xdg-mime query filetype” or “file -bi”.\n\n\n\nmimetypequeryfirst\nType: boolean\nDefault: no\n\nWhen set, the $mimetypequerycommand will be run before the mime.types lookup.\n\n\n\nmixentryformat\nType: string\nDefault: “%4n %c %-16s %a”\n\nThis variable describes the format of a remailer line on the mixmaster chain selection\nscreen. The following printf(3)-like sequences are supported:\n%n The running number on the menu.\n%c Remailer capabilities.\n%s The remailer's short name.\n%a The remailer's e-mail address.\n\n" }, { "name": "mixmaster", "content": "Type: path\nDefault: “mixmaster”\n\nThis variable contains the path to the Mixmaster binary on your system. It is used\nwith various sets of parameters to gather the list of known remailers, and to finally\nsend a message through the mixmaster chain.\n\n\n" }, { "name": "move", "content": "Type: quadoption\nDefault: no\n\nControls whether or not Mutt will move read messages from your spool mailbox to your\n$mbox mailbox, or as a result of a “mbox-hook” command.\n\n\n\nmuttlispinlineeval\nType: boolean\nDefault: no\n\nIf set, Mutt will evaluate bare parenthesis arguments to commands as MuttLisp expres‐\nsions.\n\n\n\nnarrowtree\nType: boolean\nDefault: no\n\nThis variable, when set, makes the thread tree narrower, allowing deeper threads to\nfit on the screen.\n\n\n\nnetinc\nType: number\nDefault: 10\n\nOperations that expect to transfer a large amount of data over the network will update\ntheir progress every $netinc kilobytes. If set to 0, no progress messages will be\ndisplayed.\n\nSee also $readinc, $writeinc and $netinc.\n\n\n\nnewmailcommand\nType: path\nDefault: “”\n\nIf set, Mutt will call this command after a new message is received. See the $sta‐\ntusformat documentation for the values that can be formatted into this command.\n\n\n" }, { "name": "pager", "content": "Type: path\nDefault: “builtin”\n\nThis variable specifies which pager you would like to use to view messages. The value\n“builtin” means to use the built-in pager, otherwise this variable should specify the\npathname of the external pager you would like to use.\n\nUsing an external pager may have some disadvantages: Additional keystrokes are neces‐\nsary because you can't call mutt functions directly from the pager, and screen resizes\ncause lines longer than the screen width to be badly formatted in the help menu.\n\nWhen using an external pager, also see $promptafter which defaults set.\n\n\n\npagercontext\nType: number\nDefault: 0\n\nThis variable controls the number of lines of context that are given when displaying\nthe next or previous page in the internal pager. By default, Mutt will display the\nline after the last one on the screen at the top of the next page (0 lines of con‐\ntext).\n\nThis variable also specifies the amount of context given for search results. If posi‐\ntive, this many lines will be given before a match, if 0, the match will be\ntop-aligned.\n\n\n\npagerformat\nType: string\nDefault: “-%Z- %C/%m: %-20.20n %s%* -- (%P)”\n\nThis variable controls the format of the one-line message “status” displayed before\neach message in either the internal or an external pager. The valid sequences are\nlisted in the $indexformat section.\n\n\n\npagerindexlines\nType: number\nDefault: 0\n\nDetermines the number of lines of a mini-index which is shown when in the pager. The\ncurrent message, unless near the top or bottom of the folder, will be roughly one\nthird of the way down this mini-index, giving the reader the context of a few messages\nbefore and after the message. This is useful, for example, to determine how many mes‐\nsages remain to be read in the current thread. One of the lines is reserved for the\nstatus bar from the index, so a setting of 6 will only show 5 lines of the actual in‐\ndex. A value of 0 results in no index being shown. If the number of messages in the\ncurrent folder is less than $pagerindexlines, then the index will only use as many\nlines as it needs.\n\n\n\npagerstop\nType: boolean\nDefault: no\n\nWhen set, the internal-pager will not move to the next message when you are at the end\nof a message and invoke the function.\n\n\n\npatternformat\nType: string\nDefault: “%2n %-15e %d”\n\nThis variable describes the format of the “pattern completion” menu. The following\nprintf(3)-style sequences are understood:\n%d pattern description\n%e pattern expression\n%n index number\n\npgpautodecode\nType: boolean\nDefault: no\n\nIf set, mutt will automatically attempt to decrypt traditional PGP messages whenever\nthe user performs an operation which ordinarily would result in the contents of the\nmessage being operated on. For example, if the user displays a pgp-traditional mes‐\nsage which has not been manually checked with the function,\nmutt will automatically check the message for traditional pgp.\n\n\n\npgpautoinline\nType: boolean\nDefault: no\n\nThis option controls whether Mutt generates old-style inline (traditional) PGP en‐\ncrypted or signed messages under certain circumstances. This can be overridden by use\nof the pgp menu, when inline is not required. The GPGME backend does not support this\noption.\n\nNote that Mutt might automatically use PGP/MIME for messages which consist of more\nthan a single MIME part. Mutt can be configured to ask before sending PGP/MIME mes‐\nsages when inline (traditional) would not work.\n\nAlso see the $pgpmimeauto variable.\n\nAlso note that using the old-style PGP message format is strongly deprecated. (PGP\nonly)\n\n\n\npgpcheckexit\nType: boolean\nDefault: yes\n\nIf set, mutt will check the exit code of the PGP subprocess when signing or encrypt‐\ning. A non-zero exit code means that the subprocess failed. (PGP only)\n\n\n\npgpcheckgpgdecryptstatusfd\nType: boolean\nDefault: yes\n\nIf set, mutt will check the status file descriptor output of $pgpdecryptcommand and\n$pgpdecodecommand for GnuPG status codes indicating successful decryption. This\nwill check for the presence of DECRYPTIONOKAY, absence of DECRYPTIONFAILED, and that\nall PLAINTEXT occurs between the BEGINDECRYPTION and ENDDECRYPTION status codes.\n\nIf unset, mutt will instead match the status fd output against $pgpdecryptionokay.\n(PGP only)\n\n\n\npgpclearsigncommand\nType: string\nDefault: “”\n\nThis format is used to create an old-style “clearsigned” PGP message. Note that the\nuse of this format is strongly deprecated.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npgpdecodecommand\nType: string\nDefault: “”\n\nThis format strings specifies a command which is used to decode application/pgp at‐\ntachments.\n\nThe PGP command formats have their own set of printf(3)-like sequences:\n%p Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty string other‐\nwise. Note: This may be used with a %? construct.\n%f Expands to the name of a file containing a message.\n%s Expands to the name of a file containing the signature part\nof a multipart/signed attachment when verifying it.\n%a The value of $pgpsignas if set, otherwise the value of $pgpdefaultkey.\n%r One or more key IDs (or fingerprints if available).\n\nFor examples on how to configure these formats for the various versions of PGP which\nare floating around, see the pgp and gpg sample configuration files in the samples/\nsubdirectory which has been installed on your system alongside the documentation.\n(PGP only)\n\n\n\npgpdecryptcommand\nType: string\nDefault: “”\n\nThis command is used to decrypt a PGP encrypted message.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npgpdecryptionokay\nType: regular expression\nDefault: “”\n\nIf you assign text to this variable, then an encrypted PGP message is only considered\nsuccessfully decrypted if the output from $pgpdecryptcommand contains the text.\nThis is used to protect against a spoofed encrypted message, with multipart/encrypted\nheaders but containing a block that is not actually encrypted. (e.g. simply signed\nand ascii armored text).\n\nNote that if $pgpcheckgpgdecryptstatusfd is set, this variable is ignored. (PGP\nonly)\n\n\n\npgpdefaultkey\nType: string\nDefault: “”\n\nThis is the default key-pair to use for PGP operations. It will be used for encryp‐\ntion (see $postponeencrypt and $pgpselfencrypt).\n\nIt will also be used for signing unless $pgpsignas is set.\n\nThe (now deprecated) pgpselfencryptas is an alias for this variable, and should no\nlonger be used. (PGP only)\n\n\n\npgpencryptonlycommand\nType: string\nDefault: “”\n\nThis command is used to encrypt a body part without signing it.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npgpencryptsigncommand\nType: string\nDefault: “”\n\nThis command is used to both sign and encrypt a body part.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npgpentryformat\nType: string\nDefault: “%4n %t%f %4l/0x%k %-4a %2c %u”\n\nThis variable allows you to customize the PGP key selection menu to your personal\ntaste. This string is similar to $indexformat, but has its own set of printf(3)-like\nsequences:\n%n number\n%k key id\n%u user id\n%a algorithm\n%l key length\n%f flags\n%c capabilities\n%t trust/validity of the key-uid association\n%[] date of the key where is an strftime(3) expression\n\n(PGP only)\n\n\n\npgpexportcommand\nType: string\nDefault: “”\n\nThis command is used to export a public key from the user's key ring.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npgpgetkeyscommand\nType: string\nDefault: “”\n\nThis command is invoked whenever Mutt needs to fetch the public key associated with an\nemail address. Of the sequences supported by $pgpdecodecommand, %r is the only\nprintf(3)-like sequence used with this format. Note that in this case, %r expands to\nthe email address, not the public key ID (the key ID is unknown, which is why Mutt is\ninvoking this command). (PGP only)\n\n\n\npgpgoodsign\nType: regular expression\nDefault: “”\n\nIf you assign a text to this variable, then a PGP signature is only considered veri‐\nfied if the output from $pgpverifycommand contains the text. Use this variable if\nthe exit code from the command is 0 even for bad signatures. (PGP only)\n\n\n\npgpignoresubkeys\nType: boolean\nDefault: yes\n\nSetting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, the princi‐\npal key will inherit the subkeys' capabilities. Unset this if you want to play inter‐\nesting key selection games. (PGP only)\n\n\n\npgpimportcommand\nType: string\nDefault: “”\n\nThis command is used to import a key from a message into the user's public key ring.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npgplistpubringcommand\nType: string\nDefault: “”\n\nThis command is used to list the public key ring's contents. The output format must\nbe analogous to the one used by\n\n\ngpg --list-keys --with-colons --with-fingerprint\n\n\nThis format is also generated by the muttpgpring utility which comes with mutt.\n\nNote: gpg's fixed-list-mode option should not be used. It produces a different date\nformat which may result in mutt showing incorrect key generation dates.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. Note that in this case, %r expands to the search string,\nwhich is a list of one or more quoted values such as email address, name, or keyid.\n(PGP only)\n\n\n\npgplistsecringcommand\nType: string\nDefault: “”\n\nThis command is used to list the secret key ring's contents. The output format must\nbe analogous to the one used by:\n\n\ngpg --list-keys --with-colons --with-fingerprint\n\n\nThis format is also generated by the muttpgpring utility which comes with mutt.\n\nNote: gpg's fixed-list-mode option should not be used. It produces a different date\nformat which may result in mutt showing incorrect key generation dates.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. Note that in this case, %r expands to the search string,\nwhich is a list of one or more quoted values such as email address, name, or keyid.\n(PGP only)\n\n\n\npgplongids\nType: boolean\nDefault: yes\n\nIf set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. NOTE: Inter‐\nnally, Mutt has transitioned to using fingerprints (or long key IDs as a fallback).\nThis option now only controls the display of key IDs in the key selection menu and a\nfew other places. (PGP only)\n\n\n\npgpmimeauto\nType: quadoption\nDefault: ask-yes\n\nThis option controls whether Mutt will prompt you for automatically sending a\n(signed/encrypted) message using PGP/MIME when inline (traditional) fails (for any\nreason).\n\nAlso note that using the old-style PGP message format is strongly deprecated. (PGP\nonly)\n\n\n\npgpreplyinline\nType: boolean\nDefault: no\n\nSetting this variable will cause Mutt to always attempt to create an inline (tradi‐\ntional) message when replying to a message which is PGP encrypted/signed inline. This\ncan be overridden by use of the pgp menu, when inline is not required. This option\ndoes not automatically detect if the (replied-to) message is inline; instead it relies\non Mutt internals for previously checked/flagged messages.\n\nNote that Mutt might automatically use PGP/MIME for messages which consist of more\nthan a single MIME part. Mutt can be configured to ask before sending PGP/MIME mes‐\nsages when inline (traditional) would not work.\n\nAlso see the $pgpmimeauto variable.\n\nAlso note that using the old-style PGP message format is strongly deprecated. (PGP\nonly)\n\n\n\npgpretainablesigs\nType: boolean\nDefault: no\n\nIf set, signed and encrypted messages will consist of nested multipart/signed and mul‐‐\ntipart/encrypted body parts.\n\nThis is useful for applications like encrypted and signed mailing lists, where the\nouter layer (multipart/encrypted) can be easily removed, while the inner multi‐‐\npart/signed part is retained. (PGP only)\n\n\n\npgpselfencrypt\nType: boolean\nDefault: yes\n\nWhen set, PGP encrypted messages will also be encrypted using the key in $pgpde‐\nfaultkey. (PGP only)\n\n\n\npgpshowunusable\nType: boolean\nDefault: yes\n\nIf set, mutt will display non-usable keys on the PGP key selection menu. This in‐\ncludes keys which have been revoked, have expired, or have been marked as “disabled”\nby the user. (PGP only)\n\n\n\npgpsignas\nType: string\nDefault: “”\n\nIf you have a different key pair to use for signing, you should set this to the sign‐\ning key. Most people will only need to set $pgpdefaultkey. It is recommended that\nyou use the keyid form to specify your key (e.g. 0x00112233). (PGP only)\n\n\n\npgpsigncommand\nType: string\nDefault: “”\n\nThis command is used to create the detached PGP signature for a multipart/signed\nPGP/MIME body part.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npgpsortkeys\nType: sort order\nDefault: address\n\nSpecifies how the entries in the pgp menu are sorted. The following are legal values:\naddress\nsort alphabetically by user id\nkeyid sort alphabetically by key id\ndate sort by key creation date\ntrust sort by the trust of the key\n\nIf you prefer reverse order of the above values, prefix it with “reverse-”. (PGP\nonly)\n\n\n\npgpstrictenc\nType: boolean\nDefault: yes\n\nIf set, Mutt will automatically encode PGP/MIME signed messages as quoted-printable.\nPlease note that unsetting this variable may lead to problems with non-verifyable PGP\nsignatures, so only change this if you know what you are doing. (PGP only)\n\n\n\npgptimeout\nType: number (long)\nDefault: 300\n\nThe number of seconds after which a cached passphrase will expire if not used. (PGP\nonly)\n\n\n\npgpusegpgagent\nType: boolean\nDefault: yes\n\nIf set, mutt expects a gpg-agent(1) process will handle private key passphrase\nprompts. If unset, mutt will prompt for the passphrase and pass it via stdin to the\npgp command.\n\nNote that as of version 2.1, GnuPG automatically spawns an agent and requires the\nagent be used for passphrase management. Since that version is increasingly preva‐\nlent, this variable now defaults set.\n\nMutt works with a GUI or curses pinentry program. A TTY pinentry should not be used.\n\nIf you are using an older version of GnuPG without an agent running, or another en‐\ncryption program without an agent, you will need to unset this variable. (PGP only)\n\n\n\npgpverifycommand\nType: string\nDefault: “”\n\nThis command is used to verify PGP signatures.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npgpverifykeycommand\nType: string\nDefault: “”\n\nThis command is used to verify key information from the key selection menu.\n\nThis is a format string, see the $pgpdecodecommand command for possible\nprintf(3)-like sequences. (PGP only)\n\n\n\npipedecode\nType: boolean\nDefault: no\n\nUsed in connection with the function. When unset, Mutt will pipe the\nmessages without any preprocessing. When set, Mutt will attempt to decode the messages\nfirst.\n\nAlso see $pipedecodeweed, which controls whether headers will be weeded when this is\nset.\n\n\n\npipedecodeweed\nType: boolean\nDefault: yes\n\nFor , when $pipedecode is set, this further controls whether Mutt will\nweed headers.\n\n\n\npipesep\nType: string\nDefault: “\\n”\n\nThe separator to add between messages when piping a list of tagged messages to an ex‐\nternal Unix command.\n\n\n\npipesplit\nType: boolean\nDefault: no\n\nUsed in connection with the function following . If this\nvariable is unset, when piping a list of tagged messages Mutt will concatenate the\nmessages and will pipe them all concatenated. When set, Mutt will pipe the messages\none by one. In both cases the messages are piped in the current sorted order, and the\n$pipesep separator is added after each message.\n\n\n\npopauthtryall\nType: boolean\nDefault: yes\n\nIf set, Mutt will try all available authentication methods. When unset, Mutt will\nonly fall back to other authentication methods if the previous methods are unavail‐\nable. If a method is available but authentication fails, Mutt will not connect to the\nPOP server.\n\n\n\npopauthenticators\nType: string\nDefault: “”\n\nThis is a colon-delimited list of authentication methods mutt may attempt to use to\nlog in to an POP server, in the order mutt should try them. Authentication methods\nare either “user”, “apop” or any SASL mechanism, e.g. “digest-md5”, “gssapi” or\n“cram-md5”. This option is case-insensitive. If this option is unset (the default)\nmutt will try all available methods, in order from most-secure to least-secure.\n\nExample:\n\n\nset popauthenticators=”digest-md5:apop:user”\n\n\n\n\npopcheckinterval\nType: number\nDefault: 60\n\nThis variable configures how often (in seconds) mutt should look for new mail in the\ncurrently selected mailbox if it is a POP mailbox.\n\n\n\npopdelete\nType: quadoption\nDefault: ask-no\n\nIf set, Mutt will delete successfully downloaded messages from the POP server when us‐\ning the function. When unset, Mutt will download messages but also leave\nthem on the POP server.\n\n\n\npophost\nType: string\nDefault: “”\n\nThe name of your POP server for the function. You can also specify an\nalternative port, username and password, i.e.:\n\n\n[pop[s]://][username[:password]@]popserver[:port]\n\n\nwhere “[...]” denotes an optional part.\n\n\n\npoplast\nType: boolean\nDefault: no\n\nIf this variable is set, mutt will try to use the “LAST” POP command for retrieving\nonly unread messages from the POP server when using the function.\n\n\n\npopoauthrefreshcommand\nType: string\nDefault: “”\n\nThe command to run to generate an OAUTH refresh token for authorizing your connection\nto your POP server. This command will be run on every connection attempt that uses\nthe OAUTHBEARER authentication mechanism. See “oauth” for details.\n\n\n\npoppass\nType: string\nDefault: “”\n\nSpecifies the password for your POP account. If unset, Mutt will prompt you for your\npassword when you open a POP mailbox.\n\nWarning: you should only use this option when you are on a fairly secure machine, be‐\ncause the superuser can read your muttrc even if you are the only one who can read the\nfile.\n\n\n\npopreconnect\nType: quadoption\nDefault: ask-yes\n\nControls whether or not Mutt will try to reconnect to the POP server if the connection\nis lost.\n\n\n\npopuser\nType: string\nDefault: “”\n\nYour login name on the POP server.\n\nThis variable defaults to your user name on the local machine.\n\n\n\npostindentstring\nType: string\nDefault: “”\n\nSimilar to the $attribution variable, Mutt will append this string after the inclusion\nof a message which is being replied to. For a full listing of defined printf(3)-like\nsequences see the section on $indexformat.\n\n\n" }, { "name": "postpone", "content": "Type: quadoption\nDefault: ask-yes\n\nControls whether or not messages are saved in the $postponed mailbox when you elect\nnot to send immediately.\n\nAlso see the $recall variable.\n\n\n" }, { "name": "postponed", "content": "Type: path\nDefault: “~/postponed”\n\nMutt allows you to indefinitely “postpone sending a message” which you are editing.\nWhen you choose to postpone a message, Mutt saves it in the mailbox specified by this\nvariable.\n\nAlso see the $postpone variable.\n\n\n\npostponeencrypt\nType: boolean\nDefault: no\n\nWhen set, postponed messages that are marked for encryption will be self-encrypted.\nMutt will first try to encrypt using the value specified in $pgpdefaultkey or\n$smimedefaultkey. If those are not set, it will try the deprecated $postponeen‐\ncryptas. (Crypto only)\n\n\n\npostponeencryptas\nType: string\nDefault: “”\n\nThis is a deprecated fall-back variable for $postponeencrypt. Please use $pgpde‐\nfaultkey or $smimedefaultkey. (Crypto only)\n\n\n" }, { "name": "preconnect", "content": "Type: string\nDefault: “”\n\nIf set, a shell command to be executed if mutt fails to establish a connection to the\nserver. This is useful for setting up secure connections, e.g. with ssh(1). If the\ncommand returns a nonzero status, mutt gives up opening the server. Example:\n\n\nset preconnect=”ssh -f -q -L 1234:mailhost.net:143 mailhost.net \\\nsleep 20 < /dev/null > /dev/null”\n\n\nMailbox “foo” on “mailhost.net” can now be reached as “{localhost:1234}foo”.\n\nNote: For this example to work, you must be able to log in to the remote machine with‐\nout having to enter a password.\n\n\n" }, { "name": "print", "content": "Type: quadoption\nDefault: ask-no\n\nControls whether or not Mutt really prints messages. This is set to “ask-no” by de‐\nfault, because some people accidentally hit “p” often.\n\n\n\nprintcommand\nType: path\nDefault: “lpr”\n\nThis specifies the command pipe that should be used to print messages.\n\n\n\nprintdecode\nType: boolean\nDefault: yes\n\nUsed in connection with the function. If this option is set, the mes‐\nsage is decoded before it is passed to the external command specified by $printcom‐\nmand. If this option is unset, no processing will be applied to the message when\nprinting it. The latter setting may be useful if you are using some advanced printer\nfilter which is able to properly format e-mail messages for printing.\n\nAlso see $printdecodeweed, which controls whether headers will be weeded when this\nis set.\n\n\n\nprintdecodeweed\nType: boolean\nDefault: yes\n\nFor , when $printdecode is set, this further controls whether Mutt\nwill weed headers.\n\n\n\nprintsplit\nType: boolean\nDefault: no\n\nUsed in connection with the function. If this option is set, the com‐\nmand specified by $printcommand is executed once for each message which is to be\nprinted. If this option is unset, the command specified by $printcommand is executed\nonly once, and all the messages are concatenated, with a form feed as the message sep‐\narator.\n\nThose who use the enscript(1) program's mail-printing mode will most likely want to\nset this option.\n\n\n\npromptafter\nType: boolean\nDefault: yes\n\nIf you use an external $pager, setting this variable will cause Mutt to prompt you for\na command when the pager exits rather than returning to the index menu. If unset,\nMutt will return to the index menu when the external pager exits.\n\n\n\nquerycommand\nType: path\nDefault: “”\n\nThis specifies the command Mutt will use to make external address queries. The string\nmay contain a “%s”, which will be substituted with the query string the user types.\nMutt will add quotes around the string substituted for “%s” automatically according to\nshell quoting rules, so you should avoid adding your own. If no “%s” is found in the\nstring, Mutt will append the user's query to the end of the string. See “query” for\nmore information.\n\n\n\nqueryformat\nType: string\nDefault: “%4c %t %-25.25a %-25.25n %?e?(%e)?”\n\nThis variable describes the format of the “query” menu. The following printf(3)-style\nsequences are understood:\n%a destination address\n%c current entry number\n%e extra information *\n%n destination name\n%t “*” if current entry is tagged, a space otherwise\n%>X right justify the rest of the string and pad with “X”\n%|X pad to the end of the line with “X”\n%*X soft-fill with character “X” as pad\n\nFor an explanation of “soft-fill”, see the $indexformat documentation.\n\n* = can be optionally printed if nonzero, see the $statusformat documentation.\n\n\n" }, { "name": "quit", "content": "Type: quadoption\nDefault: yes\n\nThis variable controls whether “quit” and “exit” actually quit from mutt. If this op‐\ntion is set, they do quit, if it is unset, they have no effect, and if it is set to\nask-yes or ask-no, you are prompted for confirmation when you try to quit.\n\n\n\nquoteregexp\nType: regular expression\nDefault: “^([ \\t]*[|>:}#])+”\n\nA regular expression used in the internal pager to determine quoted sections of text\nin the body of a message. Quoted text may be filtered out using the \ncommand, or colored according to the “color quoted” family of directives.\n\nHigher levels of quoting may be colored differently (“color quoted1”, “color quoted2”,\netc.). The quoting level is determined by removing the last character from the matched\ntext and recursively reapplying the regular expression until it fails to produce a\nmatch.\n\nMatch detection may be overridden by the $smileys regular expression.\n\n\n\nreadinc\nType: number\nDefault: 10\n\nIf set to a value greater than 0, Mutt will display which message it is currently on\nwhen reading a mailbox or when performing search actions such as search and limit. The\nmessage is printed after this many messages have been read or searched (e.g., if set\nto 25, Mutt will print a message when it is at message 25, and then again when it gets\nto message 50). This variable is meant to indicate progress when reading or searching\nlarge mailboxes which may take some time. When set to 0, only a single message will\nappear before the reading the mailbox.\n\nAlso see the $writeinc, $netinc and $timeinc variables and the “tuning” section of\nthe manual for performance considerations.\n\n\n\nreadonly\nType: boolean\nDefault: no\n\nIf set, all folders are opened in read-only mode.\n\n\n" }, { "name": "realname", "content": "Type: string\nDefault: “”\n\nThis variable specifies what “real” or “personal” name should be used when sending\nmessages.\n\nBy default, this is the GECOS field from /etc/passwd. Note that this variable will\nnot be used when the user has set a real name in the $from variable.\n\n\n" }, { "name": "recall", "content": "Type: quadoption\nDefault: ask-yes\n\nControls whether or not Mutt recalls postponed messages when composing a new message.\n\nSetting this variable to yes is not generally useful, and thus not recommended. Note\nthat the function can be used to manually recall postponed messages.\n\nAlso see $postponed variable.\n\n\n" }, { "name": "record", "content": "Type: path\nDefault: “~/sent”\n\nThis specifies the file into which your outgoing messages should be appended. (This\nis meant as the primary method for saving a copy of your messages, but another way to\ndo this is using the “myhdr” command to create a “Bcc:” field with your email address\nin it.)\n\nThe value of $record is overridden by the $forcename and $savename variables, and\nthe “fcc-hook” command. Also see $copy and $writebcc.\n\nMultiple mailboxes may be specified if $fccdelimiter is set to a string delimiter.\n\n\n\nreflowspacequotes\nType: boolean\nDefault: yes\n\nThis option controls how quotes from format=flowed messages are displayed in the pager\nand when replying (with $textflowed unset). When set, this option adds spaces after\neach level of quote marks, turning ”>>>foo” into ”> > > foo”.\n\nNote: If $reflowtext is unset, this option has no effect. Also, this option does not\naffect replies when $textflowed is set.\n\n\n\nreflowtext\nType: boolean\nDefault: yes\n\nWhen set, Mutt will reformat paragraphs in text/plain parts marked format=flowed. If\nunset, Mutt will display paragraphs unaltered from how they appear in the message\nbody. See RFC3676 for details on the format=flowed format.\n\nAlso see $reflowwrap, and $wrap.\n\n\n\nreflowwrap\nType: number\nDefault: 78\n\nThis variable controls the maximum paragraph width when reformatting text/plain parts\nwhen $reflowtext is set. When the value is 0, paragraphs will be wrapped at the ter‐\nminal's right margin. A positive value sets the paragraph width relative to the left\nmargin. A negative value set the paragraph width relative to the right margin.\n\nAlso see $wrap.\n\n\n\nreplyregexp\nType: regular expression\nDefault: “^(re([\\[0-9\\]+])*|aw):[ \\t]*”\n\nA regular expression used to recognize reply messages when threading and replying. The\ndefault value corresponds to the English ”Re:” and the German ”Aw:”.\n\n\n\nreplyself\nType: boolean\nDefault: no\n\nIf unset and you are replying to a message sent by you, Mutt will assume that you want\nto reply to the recipients of that message rather than to yourself.\n\nAlso see the “alternates” command.\n\n\n\nreplyto\nType: quadoption\nDefault: ask-yes\n\nIf set, when replying to a message, Mutt will use the address listed in the Reply-to:\nheader as the recipient of the reply. If unset, it will use the address in the From:\nheader field instead. This option is useful for reading a mailing list that sets the\nReply-To: header field to the list address and you want to send a private message to\nthe author of a message.\n\n\n" }, { "name": "resolve", "content": "Type: boolean\nDefault: yes\n\nWhen set, the cursor will be automatically advanced to the next (possibly undeleted)\nmessage whenever a command that modifies the current message is executed.\n\n\n\nresumedraftfiles\nType: boolean\nDefault: no\n\nIf set, draft files (specified by -H on the command line) are processed similarly to\nwhen resuming a postponed message. Recipients are not prompted for; send-hooks are\nnot evaluated; no alias expansion takes place; user-defined headers and signatures are\nnot added to the message.\n\n\n\nresumeediteddraftfiles\nType: boolean\nDefault: yes\n\nIf set, draft files previously edited (via -E -H on the command line) will have $re‐\nsumedraftfiles automatically set when they are used as a draft file again.\n\nThe first time a draft file is saved, mutt will add a header, X-Mutt-Resume-Draft to\nthe saved file. The next time the draft file is read in, if mutt sees the header, it\nwill set $resumedraftfiles.\n\nThis option is designed to prevent multiple signatures, user-defined headers, and\nother processing effects from being made multiple times to the draft file.\n\n\n\nreversealias\nType: boolean\nDefault: no\n\nThis variable controls whether or not Mutt will display the “personal” name from your\naliases in the index menu if it finds an alias that matches the message's sender. For\nexample, if you have the following alias:\n\n\nalias juser abd30425@somewhere.net (Joe User)\n\n\nand then you receive mail which contains the following header:\n\n\nFrom: abd30425@somewhere.net\n\n\nIt would be displayed in the index menu as “Joe User” instead of “abd30425@some‐\nwhere.net.” This is useful when the person's e-mail address is not human friendly.\n\n\n\nreversename\nType: boolean\nDefault: no\n\nIt may sometimes arrive that you receive mail to a certain machine, move the messages\nto another machine, and reply to some the messages from there. If this variable is\nset, the default From: line of the reply messages is built using the address where you\nreceived the messages you are replying to if that address matches your “alternates”.\nIf the variable is unset, or the address that would be used doesn't match your “alter‐\nnates”, the From: line will use your address on the current machine.\n\nAlso see the “alternates” command and $reverserealname.\n\n\n\nreverserealname\nType: boolean\nDefault: yes\n\nThis variable fine-tunes the behavior of the $reversename feature.\n\nWhen it is unset, Mutt will remove the real name part of a matching address. This al‐\nlows the use of the email address without having to also use what the sender put in\nthe real name field.\n\nWhen it is set, Mutt will use the matching address as-is.\n\nIn either case, a missing real name will be filled in afterwards using the value of\n$realname.\n\n\n\nrfc2047parameters\nType: boolean\nDefault: no\n\nWhen this variable is set, Mutt will decode RFC2047-encoded MIME parameters. You want\nto set this variable when mutt suggests you to save attachments to files named like:\n\n\n=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\n\n\nWhen this variable is set interactively, the change won't be active until you change\nfolders.\n\nNote that this use of RFC2047's encoding is explicitly prohibited by the standard, but\nnevertheless encountered in the wild.\n\nAlso note that setting this parameter will not have the effect that mutt generates\nthis kind of encoding. Instead, mutt will unconditionally use the encoding specified\nin RFC2231.\n\n\n\nsaveaddress\nType: boolean\nDefault: no\n\nIf set, mutt will take the sender's full address when choosing a default folder for\nsaving a mail. If $savename or $forcename is set too, the selection of the Fcc\nfolder will be changed as well.\n\n\n\nsaveempty\nType: boolean\nDefault: yes\n\nWhen unset, mailboxes which contain no saved messages will be removed when closed (the\nexception is $spoolfile which is never removed). If set, mailboxes are never removed.\n\nNote: This only applies to mbox and MMDF folders, Mutt does not delete MH and Maildir\ndirectories.\n\n\n\nsavehistory\nType: number\nDefault: 0\n\nThis variable controls the size of the history (per category) saved in the $his‐\ntoryfile file.\n\n\n\nsavename\nType: boolean\nDefault: no\n\nThis variable controls how copies of outgoing messages are saved. When set, a check\nis made to see if a mailbox specified by the recipient address exists (this is done by\nsearching for a mailbox in the $folder directory with the username part of the recipi‐\nent address). If the mailbox exists, the outgoing message will be saved to that mail‐\nbox, otherwise the message is saved to the $record mailbox.\n\nAlso see the $forcename variable.\n\n\n" }, { "name": "score", "content": "Type: boolean\nDefault: yes\n\nWhen this variable is unset, scoring is turned off. This can be useful to selectively\ndisable scoring for certain folders when the $scorethresholddelete variable and re‐\nlated are used.\n\n\n\nscorethresholddelete\nType: number\nDefault: -1\n\nMessages which have been assigned a score equal to or lower than the value of this\nvariable are automatically marked for deletion by mutt. Since mutt scores are always\ngreater than or equal to zero, the default setting of this variable will never mark a\nmessage for deletion.\n\n\n\nscorethresholdflag\nType: number\nDefault: 9999\n\nMessages which have been assigned a score greater than or equal to this variable's\nvalue are automatically marked ”flagged”.\n\n\n\nscorethresholdread\nType: number\nDefault: -1\n\nMessages which have been assigned a score equal to or lower than the value of this\nvariable are automatically marked as read by mutt. Since mutt scores are always\ngreater than or equal to zero, the default setting of this variable will never mark a\nmessage read.\n\n\n\nsearchcontext\nType: number\nDefault: 0\n\nFor the pager, this variable specifies the number of lines shown before search re‐\nsults. By default, search results will be top-aligned.\n\n\n\nsendcharset\nType: string\nDefault: “us-ascii:iso-8859-1:utf-8”\n\nA colon-delimited list of character sets for outgoing messages. Mutt will use the\nfirst character set into which the text can be converted exactly. If your $charset is\nnot “iso-8859-1” and recipients may not understand “UTF-8”, it is advisable to include\nin the list an appropriate widely used standard character set (such as “iso-8859-2”,\n“koi8-r” or “iso-2022-jp”) either instead of or after “iso-8859-1”.\n\nIn case the text cannot be converted into one of these exactly, mutt uses $charset as\na fallback.\n\n\n\nsendmultipartalternative\nType: quadoption\nDefault: no\n\nIf set, Mutt will generate a multipart/alternative container and an alternative part\nusing the filter script specified in $sendmultipartalternativefilter. See the sec‐\ntion “MIME Multipart/Alternative” (alternative-order).\n\nNote that enabling multipart/alternative is not compatible with inline PGP encryption.\nMutt will prompt to use PGP/MIME in that case.\n\n\n\nsendmultipartalternativefilter\nType: path\nDefault: “”\n\nThis specifies a filter script, which will convert the main (composed) message of the\nemail to an alternative format. The message will be piped to the filter's stdin. The\nexpected output of the filter is the generated mime type, e.g. text/html, followed by\na blank line, and then the converted content. See the section “MIME Multipart/Alter‐\nnative” (alternative-order).\n\n\n" }, { "name": "sendmail", "content": "Type: path\nDefault: “/usr/sbin/sendmail -oem -oi”\n\nSpecifies the program and arguments used to deliver mail sent by Mutt. Mutt expects\nthat the specified program interprets additional arguments as recipient addresses.\nMutt appends all recipients after adding a -- delimiter (if not already present). Ad‐\nditional flags, such as for $use8bitmime, $useenvelopefrom, $dsnnotify, or\n$dsnreturn will be added before the delimiter.\n\nSee also: $writebcc.\n\n\n\nsendmailwait\nType: number\nDefault: 0\n\nSpecifies the number of seconds to wait for the $sendmail process to finish before\ngiving up and putting delivery in the background.\n\nMutt interprets the value of this variable as follows:\n>0 number of seconds to wait for sendmail to finish before continuing\n0 wait forever for sendmail to finish\n<0 always put sendmail in the background without waiting\n\nNote that if you specify a value other than 0, the output of the child process will be\nput in a temporary file. If there is some error, you will be informed as to where to\nfind the output.\n\n\n" }, { "name": "shell", "content": "Type: path\nDefault: “”\n\nCommand to use when spawning a subshell. By default, the user's login shell from\n/etc/passwd is used.\n\n\n\nsidebardelimchars\nType: string\nDefault: “/.”\n\nThis contains the list of characters which you would like to treat as folder separa‐\ntors for displaying paths in the sidebar.\n\nLocal mail is often arranged in directories: `dir1/dir2/mailbox'.\n\n\nset sidebardelimchars='/'\n\n\nIMAP mailboxes are often named: `folder1.folder2.mailbox'.\n\n\nset sidebardelimchars='.'\n\n\nSee also: $sidebarshortpath, $sidebarfolderindent, $sidebarindentstring.\n\n\n\nsidebardividerchar\nType: string\nDefault: “|”\n\nThis specifies the characters to be drawn between the sidebar (when visible) and the\nother Mutt panels. ASCII and Unicode line-drawing characters are supported.\n\n\n\nsidebarfolderindent\nType: boolean\nDefault: no\n\nSet this to indent mailboxes in the sidebar.\n\nSee also: $sidebarshortpath, $sidebarindentstring, $sidebardelimchars.\n\n\n\nsidebarformat\nType: string\nDefault: “%B%* %n”\n\nThis variable allows you to customize the sidebar display. This string is similar to\n$indexformat, but has its own set of printf(3)-like sequences:\n%B Name of the mailbox\n%S * Size of mailbox (total number of messages)\n%N * Number of unread messages in the mailbox\n%n N if mailbox has new mail, blank otherwise\n%F * Number of Flagged messages in the mailbox\n%! “!” : one flagged message; “!!” : two flagged messages; “n!” : n flagged mes‐\nsages (for n > 2). Otherwise prints nothing.\n%d * @ Number of deleted messages\n%L * @ Number of messages after limiting\n%t * @ Number of tagged messages\n%>X right justify the rest of the string and pad with “X”\n%|X pad to the end of the line with “X”\n%*X soft-fill with character “X” as pad\n\n* = Can be optionally printed if nonzero @ = Only applicable to the current folder\n\nIn order to use %S, %N, %F, and %!, $mailcheckstats must be set. When thus set, a\nsuggested value for this option is ”%B%?F? [%F]?%* %?N?%N/?%S”.\n\n\n\nsidebarindentstring\nType: string\nDefault: “ ”\n\nThis specifies the string that is used to indent mailboxes in the sidebar. It de‐\nfaults to two spaces.\n\nSee also: $sidebarshortpath, $sidebarfolderindent, $sidebardelimchars.\n\n\n\nsidebarnewmailonly\nType: boolean\nDefault: no\n\nWhen set, the sidebar will only display mailboxes containing new, or flagged, mail.\n\nSee also: sidebarwhitelist.\n\n\n\nsidebarnextnewwrap\nType: boolean\nDefault: no\n\nWhen set, the command will not stop and the end of the list of\nmailboxes, but wrap around to the beginning. The command is simi‐\nlarly affected, wrapping around to the end of the list.\n\n\n\nsidebarrelativeshortpathindent\nType: boolean\nDefault: no\n\nWhen set, this option changes how $sidebarshortpath and $sidebarfolderindent per‐\nform shortening and indentation: both will look at the previous sidebar entries and\nshorten/indent relative to the most recent parent.\n\nAn example of this option set/unset for mailboxes listed in this order, with $side‐\nbarshortpath=yes, $sidebarfolderindent=yes, and $sidebarindentstring=”→”:\nmailbox\nset unset\n=a.b =a.b →→b\n=a.b.c.d\n→→c.d →→→→→→d\n=a.b.e →→e →→→→e\n\nThe second line illustrates most clearly. With this option set, =a.b.c.d is shortened\nrelative to =a.b, becoming c.d; it is also indented one place relative to =a.b. With\nthis option unset =a.b.c.d is always shortened to the last part of the mailbox, d and\nis indented three places, with respect to $folder (represented by '=').\n\nWhen set, the third line will also be indented and shortened relative to the first\nline.\n\n\n\nsidebarshortpath\nType: boolean\nDefault: no\n\nBy default the sidebar will show the mailbox's path, relative to the $folder variable.\nSetting sidebarshortpath=yes will shorten the names relative to the previous name.\nHere's an example:\nshortpath=no\nshortpath=yes shortpath=yes, folderindent=yes, indentstr=””..””\nfruit fruit fruit\nfruit.apple\napple ..apple\nfruit.banana\nbanana ..banana\nfruit.cherry\ncherry ..cherry\n\nSee also: $sidebardelimchars, $sidebarfolderindent, $sidebarindentstring.\n\n\n\nsidebarsortmethod\nType: sort order\nDefault: unsorted\n\nSpecifies how to sort mailbox entries in the sidebar. By default, the entries are\nsorted alphabetically. Valid values:\n‐ alpha (alphabetically)\n‐ count (all message count)\n‐ flagged (flagged message count)\n‐ name (alphabetically)\n‐ new (unread message count)\n‐ path (alphabetically)\n‐ unread (unread message count)\n‐ unsorted\n\nYou may optionally use the “reverse-” prefix to specify reverse sorting order (exam‐\nple: “set sidebarsortmethod=reverse-alpha”).\n\n\n\nsidebarusemailboxshortcuts\nType: boolean\nDefault: no\n\nWhen set, sidebar mailboxes will be displayed with mailbox shortcut prefixes ”=” or\n”~”.\n\nWhen unset, the sidebar will trim off a matching $folder prefix but otherwise not use\nmailbox shortcuts.\n\n\n\nsidebarvisible\nType: boolean\nDefault: no\n\nThis specifies whether or not to show sidebar. The sidebar shows a list of all your\nmailboxes.\n\nSee also: $sidebarformat, $sidebarwidth\n\n\n\nsidebarwidth\nType: number\nDefault: 30\n\nThis controls the width of the sidebar. It is measured in screen columns. For exam‐\nple: sidebarwidth=20 could display 20 ASCII characters, or 10 Chinese characters.\n\n\n\nsigdashes\nType: boolean\nDefault: yes\n\nIf set, a line containing “-- ” (note the trailing space) will be inserted before your\n$signature. It is strongly recommended that you not unset this variable unless your\nsignature contains just your name. The reason for this is because many software pack‐\nages use “-- \\n” to detect your signature. For example, Mutt has the ability to high‐\nlight the signature in a different color in the built-in pager.\n\n\n\nsigontop\nType: boolean\nDefault: no\n\nIf set, the signature will be included before any quoted or forwarded text. It is\nstrongly recommended that you do not set this variable unless you really know what you\nare doing, and are prepared to take some heat from netiquette guardians.\n\n\n" }, { "name": "signature", "content": "Type: path\nDefault: “~/.signature”\n\nSpecifies the filename of your signature, which is appended to all outgoing messages.\nIf the filename ends with a pipe (“|”), it is assumed that filename is a shell command\nand input should be read from its standard output.\n\n\n\nsimplesearch\nType: string\nDefault: “~f %s | ~s %s”\n\nSpecifies how Mutt should expand a simple search into a real search pattern. A simple\nsearch is one that does not contain any of the “~” pattern modifiers. See “patterns”\nfor more information on search patterns.\n\nFor example, if you simply type “joe” at a search or limit prompt, Mutt will automati‐\ncally expand it to the value specified by this variable by replacing “%s” with the\nsupplied string. For the default value, “joe” would be expanded to: “~f joe | ~s\njoe”.\n\n\n\nsizeshowbytes\nType: boolean\nDefault: no\n\nIf set, message sizes will display bytes for values less than 1 kilobyte. See format‐\nstrings-size.\n\n\n\nsizeshowfractions\nType: boolean\nDefault: yes\n\nIf set, message sizes will be displayed with a single decimal value for sizes from 0\nto 10 kilobytes and 1 to 10 megabytes. See formatstrings-size.\n\n\n\nsizeshowmb\nType: boolean\nDefault: yes\n\nIf set, message sizes will display megabytes for values greater than or equal to 1\nmegabyte. See formatstrings-size.\n\n\n\nsizeunitsonleft\nType: boolean\nDefault: no\n\nIf set, message sizes units will be displayed to the left of the number. See format‐\nstrings-size.\n\n\n\nsleeptime\nType: number\nDefault: 1\n\nSpecifies time, in seconds, to pause while displaying certain informational messages,\nwhile moving from folder to folder and after expunging messages from the current\nfolder. The default is to pause one second, so a value of zero for this option sup‐\npresses the pause.\n\n\n\nsmartwrap\nType: boolean\nDefault: yes\n\nControls the display of lines longer than the screen width in the internal pager. If\nset, long lines are wrapped at a word boundary. If unset, lines are simply wrapped at\nthe screen edge. Also see the $markers variable.\n\n\n" }, { "name": "smileys", "content": "Type: regular expression\nDefault: “(>From )|(:[-^]?[][)(><}{|/DP])”\n\nThe pager uses this variable to catch some common false positives of $quoteregexp,\nmost notably smileys and not consider a line quoted text if it also matches $smileys.\nThis mostly happens at the beginning of a line.\n\n\n\nsmimeaskcertlabel\nType: boolean\nDefault: yes\n\nThis flag controls whether you want to be asked to enter a label for a certificate\nabout to be added to the database or not. It is set by default. (S/MIME only)\n\n\n\nsmimecalocation\nType: path\nDefault: “”\n\nThis variable contains the name of either a directory, or a file which contains\ntrusted certificates for use with OpenSSL. (S/MIME only)\n\n\n\nsmimecertificates\nType: path\nDefault: “”\n\nSince for S/MIME there is no pubring/secring as with PGP, mutt has to handle storage\nand retrieval of keys by itself. This is very basic right now, and keys and certifi‐\ncates are stored in two different directories, both named as the hash-value retrieved\nfrom OpenSSL. There is an index file which contains mailbox-address keyid pairs, and\nwhich can be manually edited. This option points to the location of the certificates.\n(S/MIME only)\n\n\n\nsmimedecryptcommand\nType: string\nDefault: “”\n\nThis format string specifies a command which is used to decrypt applica‐‐\ntion/x-pkcs7-mime attachments.\n\nThe OpenSSL command formats have their own set of printf(3)-like sequences similar to\nPGP's:\n%f Expands to the name of a file containing a message.\n%s Expands to the name of a file containing the signature part\nof a multipart/signed attachment when verifying it.\n%k The key-pair specified with $smimedefaultkey\n%c One or more certificate IDs.\n%a The algorithm used for encryption.\n%d The message digest algorithm specified with $smimesigndigestalg.\n%C CA location: Depending on whether $smimecalocation\npoints to a directory or file, this expands to\n“-CApath $smimecalocation” or “-CAfile $smimecalocation”.\n\nFor examples on how to configure these formats, see the smime.rc in the samples/ sub‐\ndirectory which has been installed on your system alongside the documentation.\n(S/MIME only)\n\n\n\nsmimedecryptusedefaultkey\nType: boolean\nDefault: yes\n\nIf set (default) this tells mutt to use the default key for decryption. Otherwise, if\nmanaging multiple certificate-key-pairs, mutt will try to use the mailbox-address to\ndetermine the key to use. It will ask you to supply a key, if it can't find one.\n(S/MIME only)\n\n\n\nsmimedefaultkey\nType: string\nDefault: “”\n\nThis is the default key-pair to use for S/MIME operations, and must be set to the\nkeyid (the hash-value that OpenSSL generates) to work properly.\n\nIt will be used for encryption (see $postponeencrypt and $smimeselfencrypt). If\nGPGME is enabled, this is the key id displayed by gpgsm.\n\nIt will be used for decryption unless $smimedecryptusedefaultkey is unset.\n\nIt will also be used for signing unless $smimesignas is set.\n\nThe (now deprecated) smimeselfencryptas is an alias for this variable, and should\nno longer be used. (S/MIME only)\n\n\n\nsmimeencryptcommand\nType: string\nDefault: “”\n\nThis command is used to create encrypted S/MIME messages.\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmimeencryptwith\nType: string\nDefault: “aes256”\n\nThis sets the algorithm that should be used for encryption. Valid choices are\n“aes128”, “aes192”, “aes256”, “des”, “des3”, “rc2-40”, “rc2-64”, “rc2-128”. (S/MIME\nonly)\n\n\n\nsmimegetcertcommand\nType: string\nDefault: “”\n\nThis command is used to extract X509 certificates from a PKCS7 structure.\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmimegetcertemailcommand\nType: string\nDefault: “”\n\nThis command is used to extract the mail address(es) used for storing X509 certifi‐\ncates, and for verification purposes (to check whether the certificate was issued for\nthe sender's mailbox).\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmimegetsignercertcommand\nType: string\nDefault: “”\n\nThis command is used to extract only the signers X509 certificate from a S/MIME signa‐\nture, so that the certificate's owner may get compared to the email's “From:” field.\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmimeimportcertcommand\nType: string\nDefault: “”\n\nThis command is used to import a certificate via smimekeys.\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmimeisdefault\nType: boolean\nDefault: no\n\nThe default behavior of mutt is to use PGP on all auto-sign/encryption operations. To\noverride and to use OpenSSL instead this must be set. However, this has no effect\nwhile replying, since mutt will automatically select the same application that was\nused to sign/encrypt the original message. (Note that this variable can be overridden\nby unsetting $cryptautosmime.) (S/MIME only)\n\n\n\nsmimekeys\nType: path\nDefault: “”\n\nSince for S/MIME there is no pubring/secring as with PGP, mutt has to handle storage\nand retrieval of keys/certs by itself. This is very basic right now, and stores keys\nand certificates in two different directories, both named as the hash-value retrieved\nfrom OpenSSL. There is an index file which contains mailbox-address keyid pair, and\nwhich can be manually edited. This option points to the location of the private keys.\n(S/MIME only)\n\n\n\nsmimepk7outcommand\nType: string\nDefault: “”\n\nThis command is used to extract PKCS7 structures of S/MIME signatures, in order to ex‐\ntract the public X509 certificate(s).\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmimeselfencrypt\nType: boolean\nDefault: yes\n\nWhen set, S/MIME encrypted messages will also be encrypted using the certificate in\n$smimedefaultkey. (S/MIME only)\n\n\n\nsmimesignas\nType: string\nDefault: “”\n\nIf you have a separate key to use for signing, you should set this to the signing key.\nMost people will only need to set $smimedefaultkey. (S/MIME only)\n\n\n\nsmimesigncommand\nType: string\nDefault: “”\n\nThis command is used to created S/MIME signatures of type multipart/signed, which can\nbe read by all mail clients.\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. NOTE: %c and %k will default to $smimesignas if set, oth‐\nerwise $smimedefaultkey. (S/MIME only)\n\n\n\nsmimesigndigestalg\nType: string\nDefault: “sha256”\n\nThis sets the algorithm that should be used for the signature message digest. Valid\nchoices are “md5”, “sha1”, “sha224”, “sha256”, “sha384”, “sha512”. (S/MIME only)\n\n\n\nsmimesignopaquecommand\nType: string\nDefault: “”\n\nThis command is used to created S/MIME signatures of type application/x-pkcs7-signa‐‐\nture, which can only be handled by mail clients supporting the S/MIME extension.\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmimetimeout\nType: number (long)\nDefault: 300\n\nThe number of seconds after which a cached passphrase will expire if not used.\n(S/MIME only)\n\n\n\nsmimeverifycommand\nType: string\nDefault: “”\n\nThis command is used to verify S/MIME signatures of type multipart/signed.\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmimeverifyopaquecommand\nType: string\nDefault: “”\n\nThis command is used to verify S/MIME signatures of type application/x-pkcs7-mime.\n\nThis is a format string, see the $smimedecryptcommand command for possible\nprintf(3)-like sequences. (S/MIME only)\n\n\n\nsmtpauthenticators\nType: string\nDefault: “”\n\nThis is a colon-delimited list of authentication methods mutt may attempt to use to\nlog in to an SMTP server, in the order mutt should try them. Authentication methods\nare any SASL mechanism, e.g. “digest-md5”, “gssapi” or “cram-md5”. This option is\ncase-insensitive. If it is “unset” (the default) mutt will try all available methods,\nin order from most-secure to least-secure.\n\nExample:\n\n\nset smtpauthenticators=”digest-md5:cram-md5”\n\n\n\n\nsmtpoauthrefreshcommand\nType: string\nDefault: “”\n\nThe command to run to generate an OAUTH refresh token for authorizing your connection\nto your SMTP server. This command will be run on every connection attempt that uses\nthe OAUTHBEARER authentication mechanism. See “oauth” for details.\n\n\n\nsmtppass\nType: string\nDefault: “”\n\nSpecifies the password for your SMTP account. If unset, Mutt will prompt you for your\npassword when you first send mail via SMTP. See $smtpurl to configure mutt to send\nmail via SMTP.\n\nWarning: you should only use this option when you are on a fairly secure machine, be‐\ncause the superuser can read your muttrc even if you are the only one who can read the\nfile.\n\n\n\nsmtpurl\nType: string\nDefault: “”\n\nDefines the SMTP smarthost where sent messages should relayed for delivery. This\nshould take the form of an SMTP URL, e.g.:\n\n\nsmtp[s]://[user[:pass]@]host[:port]\n\n\nwhere “[...]” denotes an optional part. Setting this variable overrides the value of\nthe $sendmail variable.\n\nAlso see $writebcc.\n\n\n" }, { "name": "sort", "content": "Type: sort order\nDefault: date\n\nSpecifies how to sort messages in the “index” menu. Valid values are:\n‐ date or date-sent\n‐ date-received\n‐ from\n‐ mailbox-order (unsorted)\n‐ score\n‐ size\n‐ spam\n‐ subject\n‐ threads\n‐ to\n\nYou may optionally use the “reverse-” prefix to specify reverse sorting order (exam‐\nple: “set sort=reverse-date-sent”).\n\n\n\nsortalias\nType: sort order\nDefault: alias\n\nSpecifies how the entries in the “alias” menu are sorted. The following are legal\nvalues:\n‐ address (sort alphabetically by email address)\n‐ alias (sort alphabetically by alias name)\n‐ unsorted (leave in order specified in .muttrc)\n\n\nsortaux\nType: sort order\nDefault: date\n\nThis provides a secondary sort for messages in the “index” menu, used when the $sort\nvalue is equal for two messages.\n\nWhen sorting by threads, this variable controls how threads are sorted in relation to\nother threads, and how the branches of the thread trees are sorted. This can be set\nto any value that $sort can, except “threads” (in that case, mutt will just use\n“date-sent”). You can also specify the “last-” prefix in addition to the “reverse-”\nprefix, but “last-” must come after “reverse-”. The “last-” prefix causes messages to\nbe sorted against its siblings by which has the last descendant, using the rest of\n$sortaux as an ordering. For instance,\n\n\nset sortaux=last-date-received\n\n\nwould mean that if a new message is received in a thread, that thread becomes the last\none displayed (or the first, if you have “set sort=reverse-threads”.)\n\nNote: For reversed-threads $sort order, $sortaux is reversed again (which is not the\nright thing to do, but kept to not break any existing configuration setting).\n\n\n\nsortbrowser\nType: sort order\nDefault: alpha\n\nSpecifies how to sort entries in the file browser. By default, the entries are sorted\nalphabetically. Valid values:\n‐ alpha (alphabetically)\n‐ count\n‐ date\n‐ size\n‐ unread\n‐ unsorted\n\nYou may optionally use the “reverse-” prefix to specify reverse sorting order (exam‐\nple: “set sortbrowser=reverse-date”).\n\n\n\nsortbrowsermailboxes\nType: sort order\nDefault: unsorted\n\nSpecifies how to sort entries in the mailbox browser. By default, the entries are un‐\nsorted, displayed in the same order as listed in the “mailboxes” command. Valid val‐\nues:\n‐ alpha (alphabetically)\n‐ count\n‐ date\n‐ size\n‐ unread\n‐ unsorted\n\nYou may optionally use the “reverse-” prefix to specify reverse sorting order (exam‐\nple: “set sortbrowsermailboxes=reverse-alpha”).\n\n\n\nsortre\nType: boolean\nDefault: yes\n\nThis variable is only useful when sorting by threads with $strictthreads unset. In\nthat case, it changes the heuristic mutt uses to thread messages by subject. With\n$sortre set, mutt will only attach a message as the child of another message by sub‐\nject if the subject of the child message starts with a substring matching the setting\nof $replyregexp. With $sortre unset, mutt will attach the message whether or not\nthis is the case, as long as the non-$replyregexp parts of both messages are identi‐\ncal.\n\n\n\nspamseparator\nType: string\nDefault: “,”\n\nThis variable controls what happens when multiple spam headers are matched: if unset,\neach successive header will overwrite any previous matches value for the spam label.\nIf set, each successive match will append to the previous, using this variable's value\nas a separator.\n\n\n" }, { "name": "spoolfile", "content": "Type: path\nDefault: “”\n\nIf your spool mailbox is in a non-default place where Mutt cannot find it, you can\nspecify its location with this variable. Mutt will initially set this variable to the\nvalue of the environment variable $MAIL or $MAILDIR if either is defined.\n\n\n\nsslcacertificatesfile\nType: path\nDefault: “”\n\nThis variable specifies a file containing trusted CA certificates. Any server cer‐\ntificate that is signed with one of these CA certificates is also automatically ac‐\ncepted. (GnuTLS only)\n\nExample:\n\n\nset sslcacertificatesfile=/etc/ssl/certs/ca-certificates.crt\n\n\n\n\nsslclientcert\nType: path\nDefault: “”\n\nThe file containing a client certificate and its associated private key.\n\n\n\nsslforcetls\nType: boolean\nDefault: yes\n\nIf this variable is set, Mutt will require that all connections to remote servers be\nencrypted. Furthermore it will attempt to negotiate TLS even if the server does not\nadvertise the capability, since it would otherwise have to abort the connection any‐\nway. This option supersedes $sslstarttls.\n\n\n\nsslmindhprimebits\nType: number\nDefault: 0\n\nThis variable specifies the minimum acceptable prime size (in bits) for use in any\nDiffie-Hellman key exchange. A value of 0 will use the default from the GNUTLS li‐\nbrary. (GnuTLS only)\n\n\n\nsslstarttls\nType: quadoption\nDefault: yes\n\nIf set (the default), mutt will attempt to use STARTTLS on servers advertising the ca‐\npability. When unset, mutt will not attempt to use STARTTLS regardless of the server's\ncapabilities.\n\nNote that STARTTLS is subject to many kinds of attacks, including the ability of a ma‐\nchine-in-the-middle to suppress the advertising of support. Setting $sslforcetls is\nrecommended if you rely on STARTTLS.\n\n\n\nsslusesslv2\nType: boolean\nDefault: no\n\nIf set , Mutt will use SSLv2 when communicating with servers that request it. N.B. As\nof 2011, SSLv2 is considered insecure, and using is inadvisable. See\nhttps://tools.ietf.org/html/rfc6176 . (OpenSSL only)\n\n\n\nsslusesslv3\nType: boolean\nDefault: no\n\nIf set , Mutt will use SSLv3 when communicating with servers that request it. N.B. As\nof 2015, SSLv3 is considered insecure, and using it is inadvisable. See\nhttps://tools.ietf.org/html/rfc7525 .\n\n\n\nsslusetlsv1\nType: boolean\nDefault: no\n\nIf set , Mutt will use TLSv1.0 when communicating with servers that request it. N.B.\nAs of 2015, TLSv1.0 is considered insecure, and using it is inadvisable. See\nhttps://tools.ietf.org/html/rfc7525 .\n\n\n\nsslusetlsv11\nType: boolean\nDefault: no\n\nIf set , Mutt will use TLSv1.1 when communicating with servers that request it. N.B.\nAs of 2015, TLSv1.1 is considered insecure, and using it is inadvisable. See\nhttps://tools.ietf.org/html/rfc7525 .\n\n\n\nsslusetlsv12\nType: boolean\nDefault: yes\n\nIf set , Mutt will use TLSv1.2 when communicating with servers that request it.\n\n\n\nsslusetlsv13\nType: boolean\nDefault: yes\n\nIf set , Mutt will use TLSv1.3 when communicating with servers that request it.\n\n\n\nsslusesystemcerts\nType: boolean\nDefault: yes\n\nIf set to yes, mutt will use CA certificates in the system-wide certificate store when\nchecking if a server certificate is signed by a trusted CA. (OpenSSL only)\n\n\n\nsslverifydates\nType: boolean\nDefault: yes\n\nIf set (the default), mutt will not automatically accept a server certificate that is\neither not yet valid or already expired. You should only unset this for particular\nknown hosts, using the function.\n\n\n\nsslverifyhost\nType: boolean\nDefault: yes\n\nIf set (the default), mutt will not automatically accept a server certificate whose\nhost name does not match the host used in your folder URL. You should only unset this\nfor particular known hosts, using the function.\n\n\n\nsslverifyhostoverride\nType: string\nDefault: “”\n\nDefines an alternate host name to verify the server certificate against. This should\nnot be set unless you are sure what you are doing, but it might be useful for connec‐\ntion to a .onion host without a properly configured host name in the certificate. See\n$sslverifyhost.\n\n\n\nsslverifypartialchains\nType: boolean\nDefault: no\n\nThis option should not be changed from the default unless you understand what you are\ndoing.\n\nSetting this variable to yes will permit verifying partial certification chains, i. e.\na certificate chain where not the root, but an intermediate certificate CA, or the\nhost certificate, are marked trusted (in $certificatefile), without marking the root\nsigning CA as trusted.\n\n(OpenSSL 1.0.2b and newer only).\n\n\n\nsslciphers\nType: string\nDefault: “”\n\nContains a colon-separated list of ciphers to use when using SSL. For OpenSSL, see\nciphers(1) for the syntax of the string.\n\nFor GnuTLS, this option will be used in place of ”NORMAL” at the start of the priority\nstring. See gnutlspriorityinit(3) for the syntax and more details. (Note: GnuTLS\nversion 2.1.7 or higher is required.)\n\n\n\nstatuschars\nType: string\nDefault: “-*%A”\n\nControls the characters used by the “%r” indicator in $statusformat. The first char‐\nacter is used when the mailbox is unchanged. The second is used when the mailbox has\nbeen changed, and it needs to be resynchronized. The third is used if the mailbox is\nin read-only mode, or if the mailbox will not be written when exiting that mailbox\n(You can toggle whether to write changes to a mailbox with the opera‐\ntion, bound by default to “%”). The fourth is used to indicate that the current folder\nhas been opened in attach- message mode (Certain operations like composing a new mail,\nreplying, forwarding, etc. are not permitted in this mode).\n\n\n\nstatusformat\nType: string (localized)\nDefault: “-%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?%?B? Back:%B?%?l? %l?]---(%s/%S)-%>-(%P)---”\n\nControls the format of the status line displayed in the “index” menu. This string is\nsimilar to $indexformat, but has its own set of printf(3)-like sequences:\n%b number of mailboxes with new mail *\n%B number of backgrounded editing sessions *\n%d number of deleted messages *\n%f the full pathname of the current mailbox\n%F number of flagged messages *\n%h local hostname\n%l size (in bytes) of the current mailbox (see formatstrings-size) *\n%L size (in bytes) of the messages shown (i.e., which match the current limit)\n(see formatstrings-size) *\n%m the number of messages in the mailbox *\n%M the number of messages shown (i.e., which match the current limit) *\n%n number of new messages in the mailbox *\n%o number of old unread messages *\n%p number of postponed messages *\n%P percentage of the way through the index\n%r modified/read-only/won't-write/attach-message indicator, according to $sta‐\ntuschars\n%R number of read messages *\n%s current sorting mode ($sort)\n%S current aux sorting method ($sortaux)\n%t number of tagged messages *\n%u number of unread messages *\n%v Mutt version string\n%V currently active limit pattern, if any *\n%>X right justify the rest of the string and pad with “X”\n%|X pad to the end of the line with “X”\n%*X soft-fill with character “X” as pad\n\nFor an explanation of “soft-fill”, see the $indexformat documentation.\n\n* = can be optionally printed if nonzero\n\nSome of the above sequences can be used to optionally print a string if their value is\nnonzero. For example, you may only want to see the number of flagged messages if such\nmessages exist, since zero is not particularly meaningful. To optionally print a\nstring based upon one of the above sequences, the following construct is used:\n\n%???\n\nwhere sequencechar is a character from the table above, and optionalstring is the\nstring you would like printed if sequencechar is nonzero. optionalstring may con‐\ntain other sequences as well as normal text, but you may not nest optional strings.\n\nHere is an example illustrating how to optionally print the number of new messages in\na mailbox:\n\n%?n?%n new messages.?\n\nYou can also switch between two strings using the following construct:\n\n%??&?\n\nIf the value of sequencechar is non-zero, ifstring will be expanded, otherwise\nelsestring will be expanded.\n\nYou can force the result of any printf(3)-like sequence to be lowercase by prefixing\nthe sequence character with an underscore (“”) sign. For example, if you want to\ndisplay the local hostname in lowercase, you would use: “%h”.\n\nIf you prefix the sequence character with a colon (“:”) character, mutt will replace\nany dots in the expansion by underscores. This might be helpful with IMAP folders that\ndon't like dots in folder names.\n\n\n\nstatusontop\nType: boolean\nDefault: no\n\nSetting this variable causes the “status bar” to be displayed on the first line of the\nscreen rather than near the bottom. If $help is set, too it'll be placed at the bot‐\ntom.\n\n\n\nstrictthreads\nType: boolean\nDefault: no\n\nIf set, threading will only make use of the “In-Reply-To” and “References:” fields\nwhen you $sort by message threads. By default, messages with the same subject are\ngrouped together in “pseudo threads.”. This may not always be desirable, such as in a\npersonal mailbox where you might have several unrelated messages with the subjects\nlike “hi” which will get grouped together. See also $sortre for a less drastic way of\ncontrolling this behavior.\n\n\n" }, { "name": "suspend", "content": "Type: boolean\nDefault: yes\n\nWhen unset, mutt won't stop when the user presses the terminal's susp key, usually\n“^Z”. This is useful if you run mutt inside an xterm using a command like “xterm -e\nmutt”.\n\n\n\ntextflowed\nType: boolean\nDefault: no\n\nWhen set, mutt will generate “format=flowed” bodies with a content type of\n“text/plain; format=flowed”. This format is easier to handle for some mailing soft‐\nware, and generally just looks like ordinary text. To actually make use of this for‐\nmat's features, you'll need support in your editor.\n\nThe option only controls newly composed messages. Postponed messages, resent mes‐\nsages, and draft messages (via -H on the command line) will use the content-type of\nthe source message.\n\nNote that $indentstring is ignored when this option is set.\n\n\n\nthoroughsearch\nType: boolean\nDefault: yes\n\nAffects the ~b, ~B, and ~h search operations described in section “patterns”. If set,\nthe headers and body/attachments of messages to be searched are decoded before search‐\ning. If unset, messages are searched as they appear in the folder.\n\nUsers searching attachments or for non-ASCII characters should set this value because\ndecoding also includes MIME parsing/decoding and possible character set conversions.\nOtherwise mutt will attempt to match against the raw message received (for example\nquoted-printable encoded or with encoded headers) which may lead to incorrect search\nresults.\n\n\n\nthreadreceived\nType: boolean\nDefault: no\n\nWhen set, mutt uses the date received rather than the date sent to thread messages by\nsubject.\n\n\n" }, { "name": "tilde", "content": "Type: boolean\nDefault: no\n\nWhen set, the internal-pager will pad blank lines to the bottom of the screen with a\ntilde (“~”).\n\n\n\ntimeinc\nType: number\nDefault: 0\n\nAlong with $readinc, $writeinc, and $netinc, this variable controls the frequency\nwith which progress updates are displayed. It suppresses updates less than $timeinc\nmilliseconds apart. This can improve throughput on systems with slow terminals, or\nwhen running mutt on a remote system.\n\nAlso see the “tuning” section of the manual for performance considerations.\n\n\n" }, { "name": "timeout", "content": "Type: number\nDefault: 600\n\nWhen Mutt is waiting for user input either idling in menus or in an interactive\nprompt, Mutt would block until input is present. Depending on the context, this would\nprevent certain operations from working, like checking for new mail or keeping an IMAP\nconnection alive.\n\nThis variable controls how many seconds Mutt will at most wait until it aborts waiting\nfor input, performs these operations and continues to wait for input.\n\nA value of zero or less will cause Mutt to never time out.\n\n\n" }, { "name": "tmpdir", "content": "Type: path\nDefault: “”\n\nThis variable allows you to specify where Mutt will place its temporary files needed\nfor displaying and composing messages. If this variable is not set, the environment\nvariable $TMPDIR is used. If $TMPDIR is not set then “/var/tmp” is used.\n\n\n\ntochars\nType: string\nDefault: “ +TCFL”\n\nControls the character used to indicate mail addressed to you. The first character is\nthe one used when the mail is not addressed to your address. The second is used when\nyou are the only recipient of the message. The third is when your address appears in\nthe “To:” header field, but you are not the only recipient of the message. The fourth\ncharacter is used when your address is specified in the “Cc:” header field, but you\nare not the only recipient. The fifth character is used to indicate mail that was\nsent by you. The sixth character is used to indicate when a mail was sent to a mail‐\ning-list you subscribe to.\n\n\n" }, { "name": "trash", "content": "Type: path\nDefault: “”\n\nIf set, this variable specifies the path of the trash folder where the mails marked\nfor deletion will be moved, instead of being irremediably purged.\n\nNOTE: When you delete a message in the trash folder, it is really deleted, so that you\nhave a way to clean the trash.\n\n\n\ntsiconformat\nType: string (localized)\nDefault: “M%?n?AIL&ail?”\n\nControls the format of the icon title, as long as “$tsenabled” is set. This string\nis identical in formatting to the one used by “$statusformat”.\n\n\n\ntsenabled\nType: boolean\nDefault: no\n\nControls whether mutt tries to set the terminal status line and icon name. Most ter‐\nminal emulators emulate the status line in the window title.\n\n\n\ntsstatusformat\nType: string (localized)\nDefault: “Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?”\n\nControls the format of the terminal status line (or window title), provided that\n“$tsenabled” has been set. This string is identical in formatting to the one used by\n“$statusformat”.\n\n\n" }, { "name": "tunnel", "content": "Type: string\nDefault: “”\n\nSetting this variable will cause mutt to open a pipe to a command instead of a raw\nsocket. You may be able to use this to set up preauthenticated connections to your\nIMAP/POP3/SMTP server. Example:\n\n\nset tunnel=”ssh -q mailhost.net /usr/local/libexec/imapd”\n\n\nNote: For this example to work you must be able to log in to the remote machine with‐\nout having to enter a password.\n\nWhen set, Mutt uses the tunnel for all remote connections. Please see “account-hook”\nin the manual for how to use different tunnel commands per connection.\n\n\n\ntunnelissecure\nType: boolean\nDefault: yes\n\nWhen set, Mutt will assume the $tunnel connection does not need STARTTLS to be en‐\nabled. It will also allow IMAP PREAUTH server responses inside a tunnel to proceed.\nThis is appropriate if $tunnel uses ssh or directly invokes the server locally.\n\nWhen unset, Mutt will negotiate STARTTLS according to the sslstarttls and\nsslforcetls variables. If sslforcetls is set, Mutt will abort connecting if an\nIMAP server responds with PREAUTH. This setting is appropriate if $tunnel does not\nprovide security and could be tampered with by attackers.\n\n\n\nuncollapsejump\nType: boolean\nDefault: no\n\nWhen set, Mutt will jump to the next unread message, if any, when the current thread\nis uncollapsed.\n\n\n\nuncollapsenew\nType: boolean\nDefault: yes\n\nWhen set, Mutt will automatically uncollapse any collapsed thread that receives a new\nmessage. When unset, collapsed threads will remain collapsed. the presence of the new\nmessage will still affect index sorting, though.\n\n\n\nuse8bitmime\nType: boolean\nDefault: no\n\nWarning: do not set this variable unless you are using a version of sendmail which\nsupports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be able to send\nmail.\n\nWhen set, Mutt will invoke $sendmail with the -B8BITMIME flag when sending 8-bit mes‐\nsages to enable ESMTP negotiation.\n\n\n\nusedomain\nType: boolean\nDefault: yes\n\nWhen set, Mutt will qualify all local addresses (ones without the “@host” portion)\nwith the value of $hostname. If unset, no addresses will be qualified.\n\n\n\nuseenvelopefrom\nType: boolean\nDefault: no\n\nWhen set, mutt will set the envelope sender of the message. If $envelopefromaddress\nis set, it will be used as the sender address. If unset, mutt will attempt to derive\nthe sender from the “From:” header.\n\nNote that this information is passed to sendmail command using the -f command line\nswitch. Therefore setting this option is not useful if the $sendmail variable already\ncontains -f or if the executable pointed to by $sendmail doesn't support the -f\nswitch.\n\n\n\nusefrom\nType: boolean\nDefault: yes\n\nWhen set, Mutt will generate the “From:” header field when sending messages. If un‐\nset, no “From:” header field will be generated unless the user explicitly sets one us‐\ning the “myhdr” command.\n\n\n\nuseipv6\nType: boolean\nDefault: yes\n\nWhen set, Mutt will look for IPv6 addresses of hosts it tries to contact. If this op‐\ntion is unset, Mutt will restrict itself to IPv4 addresses. Normally, the default\nshould work.\n\n\n\nuseragent\nType: boolean\nDefault: no\n\nWhen set, mutt will add a “User-Agent:” header to outgoing messages, indicating which\nversion of mutt was used for composing them.\n\n\n" }, { "name": "visual", "content": "Type: path\nDefault: “”\n\nSpecifies the visual editor to invoke when the “~v” command is given in the built-in\neditor.\n\n\n\nwaitkey\nType: boolean\nDefault: yes\n\nControls whether Mutt will ask you to press a key after an external command has been\ninvoked by these functions: , , , , and commands.\n\nIt is also used when viewing attachments with “autoview”, provided that the corre‐\nsponding mailcap entry has a needsterminal flag, and the external program is interac‐\ntive.\n\nWhen set, Mutt will always ask for a key. When unset, Mutt will wait for a key only if\nthe external command returned a non-zero status.\n\n\n" }, { "name": "weed", "content": "Type: boolean\nDefault: yes\n\nWhen set, mutt will weed headers when displaying, forwarding, or replying to messages.\n\nAlso see $copydecodeweed, $pipedecodeweed, $printdecodeweed.\n\n\n" }, { "name": "wrap", "content": "Type: number\nDefault: 0\n\nWhen set to a positive value, mutt will wrap text at $wrap characters. When set to a\nnegative value, mutt will wrap text so that there are $wrap characters of empty space\non the right side of the terminal. Setting it to zero makes mutt wrap at the terminal\nwidth.\n\nAlso see $reflowwrap.\n\n\n\nwrapheaders\nType: number\nDefault: 78\n\nThis option specifies the number of characters to use for wrapping an outgoing mes‐\nsage's headers. Allowed values are between 78 and 998 inclusive.\n\nNote: This option usually shouldn't be changed. RFC5233 recommends a line length of 78\n(the default), so please only change this setting when you know what you're doing.\n\n\n\nwrapsearch\nType: boolean\nDefault: yes\n\nControls whether searches wrap around the end.\n\nWhen set, searches will wrap around the first (or last) item. When unset, incremental\nsearches will not wrap.\n\n\n" }, { "name": "wrapmargin", "content": "Type: number\nDefault: 0\n\n(DEPRECATED) Equivalent to setting $wrap with a negative value.\n\n\n\nwritebcc\nType: boolean\nDefault: no\n\nControls whether mutt writes out the “Bcc:” header when preparing messages to be sent.\nSome MTAs, such as Exim and Courier, do not strip the “Bcc:” header; so it is advis‐\nable to leave this unset unless you have a particular need for the header to be in the\nsent message.\n\nIf mutt is set to deliver directly via SMTP (see $smtpurl), this option does nothing:\nmutt will never write out the “Bcc:” header in this case.\n\nNote this option only affects the sending of messages. Fcc'ed copies of a message\nwill always contain the “Bcc:” header if one exists.\n\n\n\nwriteinc\nType: number\nDefault: 10\n\nWhen writing a mailbox, a message will be printed every $writeinc messages to indi‐\ncate progress. If set to 0, only a single message will be displayed before writing a\nmailbox.\n\nAlso see the $readinc, $netinc and $timeinc variables and the “tuning” section of\nthe manual for performance considerations.\n\n\n" } ] }, "SEE ALSO": { "content": "iconv(1), iconv(3), mailcap(5), maildir(5), mbox(5), mutt(1), printf(3), regex(7), strf‐‐\ntime(3)\n\nThe Mutt Manual\n\nThe Mutt home page: http://www.mutt.org/\n", "subsections": [] }, "AUTHOR": { "content": "Michael Elkins, and others. Use to contact the developers.\n\n\n\nUnix January 2019 muttrc(5)", "subsections": [] } }, "summary": "muttrc - Configuration file for the Mutt Mail User Agent", "flags": [], "examples": [], "see_also": [ { "name": "iconv", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/iconv/1/json" }, { "name": "iconv", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/iconv/3/json" }, { "name": "mailcap", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/mailcap/5/json" }, { "name": "maildir", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/maildir/5/json" }, { "name": "mbox", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/mbox/5/json" }, { "name": "mutt", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/mutt/1/json" }, { "name": "printf", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/printf/3/json" }, { "name": "regex", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/regex/7/json" }, { "name": "time", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/time/3/json" } ] }