Under Development
stars

Send Options#

$abort_noattach#

Description:

Abort sending the email if attachments are missing

Type:

Quad-Option

Default:
set abort_noattach = no

If set to yes, when composing messages containing the regular expression specified by $abort_noattach_regex and no attachments are given, composition will be aborted. If set to no, composing messages as such will never be aborted.

Example:

set abort_noattach_regex = "\\<attach(|ed|ments?)\\>"

$abort_noattach_regex#

Description:

Regex to match text indicating attachments are expected

Type:

Regular Expression

Notes:

Localised String, Smart Case

Default:
set abort_noattach_regex = "\\<(attach|attached|attachments?)\\>"

Specifies a regular expression to match against the body of the message, to determine if an attachment was mentioned but mistakenly forgotten. If it matches, $abort_noattach will be consulted to determine if message sending will be aborted.


$abort_nosubject#

Description:

Abort creating the email if subject is missing

Type:

Quad-Option

Default:
set abort_nosubject = ask-yes

If set to yes, when composing messages and no subject is given at the subject prompt, composition will be aborted. If set to no, composing messages with no subject given at the subject prompt will never be aborted.


$abort_unmodified#

Description:

Abort the sending if the message hasn’t been edited

Type:

Quad-Option

Default:
set abort_unmodified = yes

If set to yes, composition will automatically abort after editing the message body if no changes are made to the file (this check only happens after the first edit of the file). When set to no, composition will never be aborted.


$allow_8bit#

Description:

Allow 8-bit messages, don’t use quoted-printable or base64

Type:

Boolean

Default:
set allow_8bit = yes

Controls whether 8-bit data is converted to 7-bit using either Quoted-Printable or Base64 encoding when sending mail.


$ask_bcc#

Description:

Ask the user for the blind-carbon-copy recipients

Type:

Boolean

Default:
set ask_bcc = no

If set, NeoMutt will prompt you for blind-carbon-copy, Bcc:, recipients before editing an outgoing message.


$ask_cc#

Description:

Ask the user for the carbon-copy recipients

Type:

Boolean

Default:
set ask_cc = no

If set, NeoMutt will prompt you for carbon-copy, Cc:, recipients before editing the body of an outgoing message.


$ask_followup_to#

Description:

Ask the user for follow-up groups before editing

Type:

Boolean

Default:
set ask_followup_to = no

If set, NeoMutt will prompt you for follow-up groups before editing the body of an outgoing message.


$ask_x_comment_to#

Description:

Ask the user for the X-Comment-To field before editing

Type:

Boolean

Default:
set ask_x_comment_to = no

If set, NeoMutt will prompt you for X-Comment-To: field before editing the body of an outgoing message.


$attach_charset#

Description:

When attaching files, use one of these character sets

Type:

String List

Notes:

Colon-separated, Allow Empty

Default:

(empty)

set attach_charset = ""

A colon-separated list of character encoding schemes for text file attachments. NeoMutt uses this setting to guess which encoding files being attached are encoded in to convert them to a proper character set given in $send_charset.

If unset, the value of $charset will be used instead.

For example, the following configuration would work for Japanese text handling:

set attach_charset = "iso-2022-jp:euc-jp:shift_jis:utf-8"

Note

for Japanese users, “iso-2022-*” must be put at the head of the value as shown above if included.


$attribution_intro#

Description:

Message to start a reply, “On DATE, PERSON wrote:”

Type:

Expando

Notes:

Localised String, Pipe Support

Default:
set attribution_intro = "On %d, %n wrote:"
Alternative:
set attribution_intro = "On %{date-format}, %{name} wrote:"

This string will precede a replied-to message which is quoted in the main body of the reply (this is the case when $include is set).


$attribution_locale#

Description:

Locale for dates in the $attribution message

Type:

String

Default:

(empty)

set attribution_locale = ""

The locale used by strftime(3) to format dates in the attribution strings. Valid values are the strings your system accepts for the locale environment variable $LC_TIME.

Allow the attribution date format to be customized by recipient or folder using hooks. By default, NeoMutt will use your locale environment, so there is no need to set this except to override that default.


$attribution_trailer#

Description:

Suffix message to add after reply text

Type:

Expando

Notes:

Pipe Support

Default:

(empty)

set attribution_trailer = ""

Similar to the $attribution_intro option, this is the string that will come after a replied-to message which is quoted in the main body of the reply (this is the case when $include is set).


$bounce_delivered#

Description:

Add Delivered-To to bounced messages

Type:

Boolean

Default:
set bounce_delivered = yes

When this option is set, NeoMutt will include Delivered-To: headers when bouncing messages. Postfix users may wish to unset this option.


$confirm_empty_to#

Description:

Ask for a confirmation before sending an email with an empty To: recipients list

Type:

Boolean

Default:
set confirm_empty_to = no

When set, NeoMutt will prompt for confirmation when sending an e-mail with an empty To: recipients list.


$content_type#

Description:

Default Content-Type for newly composed messages

Type:

String

Default:
set content_type = "text/plain"

Sets the default Content-Type: for the body of newly composed messages.


$crypt_auto_encrypt#

Description:

Automatically PGP encrypt all outgoing mail

Type:

Boolean

Scope:

Crypto only

Default:
set crypt_auto_encrypt = no

Setting this option will cause NeoMutt to always attempt to PGP encrypt outgoing messages. This is probably only useful in connection to the :send-hook command. It can be overridden by use of the pgp menu, when encryption is not required or signing is requested as well. If $smime_is_default is set, then OpenSSL is used instead to create S/MIME messages and settings can be overridden by use of the smime menu instead.


$crypt_auto_pgp#

Description:

Allow automatic PGP functions

Type:

Boolean

Default:
set crypt_auto_pgp = yes

Control whether NeoMutt may automatically enable PGP encryption/signing for messages.


$crypt_auto_sign#

Description:

Automatically PGP sign all outgoing mail

Type:

Boolean

Scope:

Crypto only

Default:
set crypt_auto_sign = no

Setting this option will cause NeoMutt to always attempt to cryptographically sign outgoing messages. This can be overridden by use of the pgp menu, when signing is not required or encryption is requested as well. If $smime_is_default is set, then OpenSSL is used instead to create S/MIME messages and settings can be overridden by use of the smime menu instead of the pgp menu.


$crypt_auto_smime#

Description:

Allow automatic SMIME functions

Type:

Boolean

Default:
set crypt_auto_smime = yes

Control whether NeoMutt may automatically enable S/MIME encryption/signing for messages.


$crypt_reply_encrypt#

Description:

Encrypt replies to encrypted messages

Type:

Boolean

Scope:

Crypto only

Default:
set crypt_reply_encrypt = yes

If set, automatically PGP or OpenSSL encrypt replies to messages which are encrypted.


$crypt_reply_sign#

Description:

Sign replies to signed messages

Type:

Boolean

Scope:

Crypto only

Default:
set crypt_reply_sign = no

If set, automatically PGP or OpenSSL sign replies to messages which are signed.

Note

this does not work on messages that are encrypted and signed!


$crypt_reply_sign_encrypted#

Description:

Sign replies to encrypted messages

Type:

Boolean

Scope:

Crypto only

Default:
set crypt_reply_sign_encrypted = no

If set, automatically PGP or OpenSSL sign replies to messages which are encrypted. This makes sense in combination with $crypt_reply_encrypt, because it allows you to sign all messages which are automatically encrypted. This works around the problem noted in $crypt_reply_sign, that NeoMutt is not able to find out whether an encrypted message is also signed.


$dsn_notify#

Description:

Request notification for message delivery or delay

Type:

String

Default:

(empty)

set dsn_notify = ""

Set the request for when notification is returned. The string consists of a comma separated list (no spaces!) of one or more of the following: never, to never request notification, failure, to request notification on transmission failure, delay, to be notified of message delays, success, to be notified of successful transmission.

Example:

set dsn_notify = "failure,delay"

Note

When using $sendmail for delivery, you should not enable this unless you are either using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)-compatible interface supporting the -N option for DSN. For SMTP delivery, DSN support is auto-detected so that it depends on the server whether DSN will be used or not.


$dsn_return#

Description:

What to send as a notification of message delivery or delay

Type:

String

Default:

(empty)

set dsn_return = ""

Control how much of your message is returned in DSN messages. It may be set to either hdrs to return just the message header, or full to return the full message.

Example:

set dsn_return = "hdrs"

Note

When using $sendmail for delivery, you should not enable this unless you are either using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)-compatible interface supporting the -R option for DSN. For SMTP delivery, DSN support is auto-detected so that it depends on the server whether DSN will be used or not.


$empty_subject#

Description:

Subject to use when replying to an email with none

Type:

String

Default:
set empty_subject = "Re: your mail"

Specify the subject to use when replying to an email with an empty Subject:. It defaults to “Re: your mail”.


$encode_from#

Description:

Encode From as “quote-printable” at the beginning of lines

Type:

Boolean

Default:
set encode_from = no

When set, NeoMutt will quoted-printable encode messages when they contain the string “From “ (note the trailing space) in the beginning of a line. This is useful to avoid the tampering certain mail delivery and transport agents tend to do with messages (in order to prevent tools from misinterpreting the line as a mbox message separator).


$fast_reply#

Description:

Don’t prompt for the recipients and subject when replying/forwarding

Type:

Boolean

Default:
set fast_reply = no

When set, the initial prompt for recipients (To:, Cc:, Bcc:) and subject are skipped when the relevant information is already provided. These cases include replying to messages and passing the relevant command line arguments. The initial prompt for recipients is also skipped when composing a new message to the current message sender, while the initial prompt for subject is also skipped when forwarding messages.

Note

this option has no effect when the $auto_edit option is set.


$fcc_attach#

Description:

Save sent message with all their attachments

Type:

Quad-Option

Default:
set fcc_attach = yes

Control whether attachments on outgoing messages are saved along with the main body of your message.

Note

$fcc_before_send forces the default (set) behavior of this option.


$fcc_before_send#

Description:

Save FCCs before sending the message

Type:

Boolean

Default:
set fcc_before_send = no

When this option is set, FCCs will occur before sending the message. Before sending, the message cannot be manipulated, so it will be stored the exact same as sent: $fcc_attach and $fcc_clear will be ignored (using their default values).

When unset, the default, FCCs will occur after sending. options $fcc_attach and $fcc_clear will be respected, allowing it to be stored without attachments or encryption/signing if desired.


$fcc_clear#

Description:

Save sent messages unencrypted and unsigned

Type:

Boolean

Scope:

PGP only

Default:
set fcc_clear = no

When this option is set, FCCs will be stored unencrypted and unsigned, even when the actual message is encrypted and/or signed.

Note

$fcc_before_send forces the default (unset) behavior of this option.


$followup_to#

Description:

Add the Mail-Followup-To header is generated when sending mail

Type:

Boolean

Default:
set followup_to = yes

Controls whether or not the Mail-Followup-To: header field is generated when sending mail. When set, NeoMutt will generate this field when you are replying to a known mailing list, specified with the :subscribe or :lists commands.

This field has two purposes. First, preventing you from receiving duplicate copies of replies to messages which you send to mailing lists, and second, ensuring that you do get a reply separately for any messages sent to known lists to which you are not subscribed.

The header will contain only the list’s address for subscribed lists, and both the list address and your own email address for unsubscribed lists. Without this header, a group reply to your message sent to a subscribed list will be sent to both the list and your address, resulting in two copies of the same email for you.


$forward_attachments#

Description:

Forward attachments when forwarding a message

Type:

Quad-Option

Default:
set forward_attachments = ask-yes

When forwarding inline (i.e. $mime_forward unset or answered with “no” and $forward_decode set), attachments which cannot be decoded in a reasonable manner will be attached to the newly composed message if this quadoption is set or answered with “yes”.


$forward_attribution_intro#

Description:

Prefix message for forwarded messages

Type:

Expando

Notes:

Localised String, Pipe Support

Default:
set forward_attribution_intro = "----- Forwarded message from %f -----"
Alternative:
set forward_attribution_intro = "----- Forwarded message from %{from-full} -----"

This is the string that will precede a message which has been forwarded in the main body of a message (when $mime_forward is unset).


$forward_attribution_trailer#

Description:

Suffix message for forwarded messages

Type:

Expando

Notes:

Localised String, Pipe Support

Default:
set forward_attribution_trailer = "----- End forwarded message -----"

This is the string that will follow a message which has been forwarded in the main body of a message (when $mime_forward is unset).


$forward_decrypt#

Description:

Decrypt the message when forwarding it

Type:

Boolean

Default:
set forward_decrypt = yes

Controls the handling of encrypted messages when forwarding a message. When set, the outer layer of encryption is stripped off. Only used if $mime_forward is set and $mime_forward_decode is unset.


$forward_edit#

Description:

Automatically start the editor when forwarding a message

Type:

Quad-Option

Default:
set forward_edit = yes

This quadoption controls whether or not the user is automatically placed in the editor when forwarding messages. For those who always want to forward with no modification, use a setting of “no”.


$forward_format#

Description:

Format string to control the subject when forwarding a message

Type:

Expando

Notes:

Not Empty, Pipe Support

Default:
set forward_format = "[%a: %s]"
Alternative:
set forward_format = "[%{from}: %{subject}]"

Control the default subject when forwarding a message.


$forward_references#

Description:

Set the In-Reply-To and References headers when forwarding a message

Type:

Boolean

Default:
set forward_references = no

When set, forwarded messages set the In-Reply-To: and References: headers in the same way as normal replies would. Hence the forwarded message becomes part of the original thread instead of starting a new one.


$greeting#

Description:

Greeting string added to the top of all messages

Type:

Expando

Notes:

Pipe Support

Default:

(empty)

set greeting = ""

Specify the format of the greeting string. This string is added to the top of every outgoing message.

Format Sequences

Short

Long Name

Description

%n

%{real-name}

Recipient’s real name

%u

%{user-name}

User (login) name of recipient

%v

%{first-name}

First name of recipient


$hdrs#

Description:

Add custom headers to outgoing mail

Type:

Boolean

Default:
set hdrs = yes

When unset, the header fields normally added by the :my-header command are not created. Must be unset before composing a new message or replying in order to take effect. If set, the user defined header fields are added to every new message.


$hidden_host#

Description:

Don’t use the hostname, just the domain, when generating the message id

Type:

Boolean

Default:
set hidden_host = no

When set, NeoMutt will skip the host name part of $hostname option when adding the domain part to addresses.


$honor_followup_to#

Description:

Honour the Mail-Followup-To header when group replying

Type:

Quad-Option

Default:
set honor_followup_to = yes

Control whether a Mail-Followup-To: header is honored when group-replying to a message.


$ignore_list_reply_to#

Description:

Ignore the Reply-To header when using <reply> on a mailing list

Type:

Boolean

Default:
set ignore_list_reply_to = no

Affects the behavior of the <reply> function when replying to messages from mailing lists (as defined by the :subscribe or :lists commands).
When set, if the Reply-To: field is set to the same value as the To: field, NeoMutt assumes that the Reply-To: field was set by the mailing list to automate responses to the list, and will ignore this field. To direct a response to the mailing list when this option is set, use the <list-reply> function; <group-reply> will reply to both the sender and the list.


$include#

Description:

Include a copy of the email that’s being replied to

Type:

Quad-Option

Default:
set include = ask-yes

Controls whether or not a copy of the message(s) you are replying to is included in your reply.


$inews_command#

Description:

External command to post news articles

Type:

Expando (Command String)

Notes:

Pipe Support

Default:

(empty)

set inews_command = ""

Specify the format of a command used to deliver news posts. If unset, NeoMutt posts article using current connection to news server.

Format Sequences

Short

Description

%a

account url

%p

port

%P

port if specified

%s

news server name

%S

url schema

%u

username

Example:

set inews_command = "/usr/local/bin/inews -hS"

$message_id_format#

Description:

Format string for customising the Message-ID

Type:

Expando

Notes:

Pipe Support

Default:
set message_id_format = "<%z@%f>"
Alternative:
set message_id_format = "<%{random_12}@%{hostname}>"

Specify the format of the Message-ID: email header.

Warning

The Message-ID: value follows a strict syntax, and you are responsible for ensuring correctness if you change this from the default.

In particular, the value must follow the syntax in RFC 5322: "<" id-left "@" id-right ">". No spaces are allowed, and id-left should follow the dot-atom-text syntax in the RFC. The id-right should generally be left as %f.

If unset, NeoMutt will use a long random format.

If the format doesn’t begin/end with <, > they will be added.

The old Message-ID format can be used by setting this to: <%Y%02m%02d%02H%02M%02S.G%c%p@%f>

Format Sequences

Short

Long Name

Description

%c

%{counter}

Step counter looping from A to Z

%d

%{day}

Current day of the month (GMT)

%f

%{hostname}

$hostname

%H

%{hour}

Current hour using a 24-hour clock (GMT)

%m

%{minute}

Current month number (GMT)

%M

%{month}

Current minute of the hour (GMT)

%p

%{pid}

Pid of the running neomutt process

%r

%{random_3}

3 bytes of pseudo-random data encoded in Base64

%S

%{second}

Current second of the minute (GMT)

%x

%{random_1}

1 byte of pseudo-random data hex encoded (example: 1b)

%Y

%{year}

Current year using 4 digits (GMT)

%z

%{random_12}

4 byte timestamp + 8 bytes of pseudo-random data encoded in Base64


$me_too#

Description:

Remove the user’s address from the list of recipients

Type:

Boolean

Default:
set me_too = no

If unset, NeoMutt will remove your address (see the :alternates command) from the list of recipients when replying to a message.


$mime_forward_decode#

Description:

Decode the forwarded message before attaching it

Type:

Boolean

Default:
set mime_forward_decode = no

Controls the decoding of complex MIME messages into text/plain when forwarding a message while $mime_forward is set. Otherwise $forward_decode is used instead.


$mime_type_query_command#

Description:

External command to determine the MIME type of an attachment

Type:

Command (String)

Default:

(empty)

set mime_type_query_command = ""

This specifies a command to run, to determine the mime type of a new attachment when composing a message. Unless $mime_type_query_first is set, this will only be run if the attachment’s extension is not found in the mime.types file.

The string may contain a %s, which will be substituted with the attachment filename. NeoMutt will add quotes around the string substituted for %s automatically according to shell quoting rules, so you should avoid adding your own. If no %s is found in the string, NeoMutt will append the attachment filename to the end of the string.

The command should output a single line containing the attachment’s mime type.

Suggested values are xdg-mime query filetype or file -bi.


$mime_type_query_first#

Description:

Run the $mime_type_query_command before the mime.types lookup

Type:

Boolean

Default:
set mime_type_query_first = no

When set, the $mime_type_query_command will be run before the mime.types lookup.


$nm_record#

Description:

If the $record mailbox (sent mail) should be indexed

Type:

Boolean

Default:
set nm_record = no

Specify whether, when writing a just-sent message to the $record, the message should also be added to the notmuch DB. Replies inherit the notmuch tags from the original message.

See also

$nm_record_tags for how to modify the set of notmuch tags assigned to sent messages written to the record


$pgp_reply_inline#

Description:

Reply using old-style inline PGP messages (not recommended)

Type:

Boolean

Scope:

PGP only

Default:
set pgp_reply_inline = no

Setting this option will cause NeoMutt to always attempt to create an inline (traditional) message when replying to a message which is PGP encrypted/signed inline. This can be overridden by use of the pgp menu, when inline is not required. Does not automatically detect if the (replied-to) message is inline; instead it relies on NeoMutt internals for previously checked/flagged messages.

Note

NeoMutt might automatically use PGP/MIME for messages which consist of more than a single MIME part. NeoMutt can be configured to ask before sending PGP/MIME messages when inline (traditional) would not work.

See also

$pgp_mime_auto

Warning

Using the old-style PGP message format is strongly deprecated


$postpone_encrypt#

Description:

Self-encrypt postponed messages

Type:

Boolean

Scope:

Crypto only

Default:
set postpone_encrypt = no

When set, postponed messages that are marked for encryption will be self-encrypted. NeoMutt will first try to encrypt using the value specified in $pgp_default_key or $smime_default_key.


$postpone_encrypt_as#

Description:

Fallback encryption key for postponed messages

Type:

String

Default:

(empty)

set postpone_encrypt_as = ""

When set, NeoMutt will use this as a fallback encryption key for postponed messages.


$recall#

Description:

Recall postponed mesaages when asked to compose a message

Type:

Quad-Option

Default:
set recall = ask-yes

Controls whether or not NeoMutt recalls postponed messages when composing a new message.

Setting this option to yes is not generally useful, and thus not recommended.

Note

<recall-message> can be used to manually recall postponed messages

See also

$postponed


$reply_self#

Description:

Really reply to yourself, when replying to your own email

Type:

Boolean

Default:
set reply_self = no

If unset and you are replying to a message sent by you, NeoMutt will assume that you want to reply to the recipients of that message rather than to yourself.

See also

:alternates


$reply_to#

Description:

Address to use as a Reply-To header

Type:

Quad-Option

Default:
set reply_to = ask-yes

If set, when replying to a message, NeoMutt will use the address listed in the Reply-to: header as the recipient of the reply. If unset, it will use the address in the From: header field instead. Useful for reading a mailing list that sets the Reply-To: header field to the list address and you want to send a private message to the author of a message.


$reply_with_xorig#

Description:

Create From header from X-Original-To header

Type:

Boolean

Default:
set reply_with_xorig = no

Provide a toggle. When active, the From: header will be extracted from the current mail’s ‘X-Original-To:’ header. This setting does not have precedence over $reverse_real_name.

Assuming $fast_reply is disabled, this option will prompt the user with a prefilled From: header.


$resume_draft_files#

Description:

Process draft files like postponed messages

Type:

Boolean

Default:
set resume_draft_files = no

If set, draft files (specified by -H on the command line) are processed similarly to when resuming a postponed message. Recipients are not prompted for; send-hooks are not evaluated; no alias expansion takes place; user-defined headers and signatures are not added to the message.


$reverse_name#

Description:

Set the From from the address the email was sent to

Type:

Boolean

Default:
set reverse_name = no

It may sometimes arrive that you receive mail to a certain machine, move the messages to another machine, and reply to some the messages from there. If this option is set, the default From: line of the reply messages is built using the address where you received the messages you are replying to if that address matches your :alternates.
If the option is unset, or the address that would be used doesn’t match your :alternates, the From: line will use your address on the current machine.


$reverse_real_name#

Description:

Set the From from the full To address the email was sent to

Type:

Boolean

Default:
set reverse_real_name = yes

Fine-tune the behavior of the $reverse_name feature.

When it is unset, NeoMutt will remove the real name part of a matching address. This allows the use of the email address without having to also use what the sender put in the real name field.

When it is set, NeoMutt will use the matching address as-is.

In either case, a missing real name will be filled in afterwards using the value of $real_name.


$sendmail#

Description:

External command to send email

Type:

Command (String)

Default:
set sendmail = SENDMAIL " -oem -oi"

Specifies the program and arguments used to deliver mail sent by NeoMutt. NeoMutt expects that the specified program interprets additional arguments as recipient addresses. NeoMutt appends all recipients after adding a -- delimiter (if not already present).
Additional flags, such as for $use_8bit_mime, $use_envelope_from, $dsn_notify, or $dsn_return will be added before the delimiter.

Note

This command is invoked differently from most other commands in NeoMutt. It is tokenized by space, and invoked directly via execvp(3) with an array of arguments - so commands or arguments with spaces in them are not supported. The shell is not used to run the command, so shell quoting is also not supported.

See also

$write_bcc


$sendmail_wait#

Description:

Time to wait for sendmail to finish

Type:

Number

Default:
set sendmail_wait = 0

Specifies the number of seconds to wait for the $sendmail process to finish before giving up and putting delivery in the background.

NeoMutt interprets the value of this option as follows:

Value

Description

>0

number of seconds to wait for sendmail to finish before continuing

0

wait forever for sendmail to finish

<0

always put sendmail in the background without waiting

Note that if you specify a value other than 0, the output of the child process will be put in a temporary file. If there is some error, you will be informed as to where to find the output.


$signature#

Description:

File containing a signature to append to all mail

Type:

Path (String)

Notes:

File only, Pipe Support

Default:
set signature = "~/.signature"

Specifies the filename of your signature, which is appended to all outgoing messages.


$sig_dashes#

Description:

Insert -- before the signature

Type:

Boolean

Default:
set sig_dashes = yes

If set, a line containing -- (note the trailing space) will be inserted before your $signature. It is strongly recommended that you not unset this option unless your signature contains just your name. The reason for this is because many software packages use -- \n to detect your signature. For example, NeoMutt has the ability to highlight the signature in a different color in the built-in pager.


$sig_on_top#

Description:

Insert the signature before the quoted text

Type:

Boolean

Default:
set sig_on_top = no

If set, the signature will be included before any quoted or forwarded text.

Warning

Do not set this option unless you really know what you are doing, and are prepared to take some heat from netiquette guardians.


$smtp_authenticators#

Description:

List of allowed authentication methods (colon-separated)

Type:

String List

Notes:

Case Insensitive, Colon-separated

Default:

(empty)

set smtp_authenticators = ""

This is a colon-separated list of authentication methods NeoMutt may attempt to use to log in to an SMTP server, in the order NeoMutt should try them. Authentication methods are any SASL mechanism, e.g. plain, digest-md5, gssapi or cram-md5. If it is unset (the default) NeoMutt will try all available methods, in order from most-secure to least-secure. Support for the plain mechanism is bundled; other mechanisms are provided by an external SASL library (look for ‘+sasl’ in the output of neomutt -v).

Example:

set smtp_authenticators = "digest-md5:cram-md5"

$smtp_oauth_refresh_command#

Description:

External command to generate OAUTH refresh token

Type:

Command (String)

Notes:

Sensitive

Default:

(empty)

set smtp_oauth_refresh_command = ""

The command to run to generate an OAUTH refresh token for authorizing your connection to your SMTP server. This command will be run on every connection attempt that uses the OAUTHBEARER or XOAUTH2 authentication mechanisms.


$smtp_pass#

Description:

Password for the SMTP server

Type:

String

Notes:

Sensitive

Default:

(empty)

set smtp_pass = ""

Specifies the password for your SMTP account. If unset, NeoMutt will prompt you for your password when you first send mail via SMTP.

See also

$smtp_url to configure NeoMutt to send mail via SMTP

Warning

Only use this option when you are on a fairly secure machine, because the superuser can read your neomuttrc even if you are the only one who can read the file.


$smtp_url#

Description:

URL of the SMTP server

Type:

String

Notes:

Sensitive

Default:

(empty)

set smtp_url = ""

Defines the SMTP smarthost where sent messages should relayed for delivery. This should take the form of an SMTP URL, e.g.:

smtp[s]://[user[:pass]@]host[:port]

where “[…]” denotes an optional part. Setting this option overrides the value of the $sendmail option.

See also

$write_bcc


$smtp_user#

Description:

Username for the SMTP server

Type:

String

Notes:

Sensitive

Default:

(empty)

set smtp_user = ""

The username for the SMTP server.

Defaults to your user name on the local machine.#

$user_agent#

Description:

Add a User-Agent header to outgoing mail

Type:

Boolean

Default:
set user_agent = no

When set, NeoMutt will add a User-Agent: header to outgoing messages, indicating which version of NeoMutt was used for composing them.


$use_8bit_mime#

Description:

Use 8-bit messages and ESMTP to send messages

Type:

Boolean

Default:
set use_8bit_mime = no

Warning

Do not set this option unless you are using a version of sendmail which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be able to send mail.

When set, NeoMutt will invoke $sendmail with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation.


$use_envelope_from#

Description:

Set the envelope sender of the message

Type:

Boolean

Default:
set use_envelope_from = no

When set, NeoMutt will set the envelope sender of the message. If $envelope_from_address is set, it will be used as the sender address. If unset, NeoMutt will attempt to derive the sender from the From: header.

Note that this information is passed to sendmail command using the -f command line switch. Therefore setting this option is not useful if the $sendmail option already contains -f or if the executable pointed to by $sendmail doesn’t support the -f switch.


$use_from#

Description:

Set the From header for outgoing mail

Type:

Boolean

Default:
set use_from = yes

When set, NeoMutt will generate the From: header field when sending messages. If unset, no From: header field will be generated unless the user explicitly sets one using the :my-header command.


$wrap_headers#

Description:

Width to wrap headers in outgoing messages

Type:

Number

Notes:

Not Negative

Default:
set wrap_headers = 78

Specify the number of characters to use for wrapping an outgoing message’s headers. Allowed values are between 78 and 998 inclusive.

Warning

Usually shouldn’t be changed. RFC5233 recommends a line length of 78 (the default), so please only change this setting when you know what you’re doing.


$write_bcc#

Description:

Write out the Bcc: field when preparing to send a mail

Type:

Boolean

Default:
set write_bcc = no

Controls whether NeoMutt writes out the Bcc: header when preparing messages to be sent. Some MTAs, such as Exim and Courier, do not strip the Bcc: header; so it is advisable to leave this unset unless you have a particular need for the header to be in the sent message.

If NeoMutt is set to deliver directly via SMTP(see $smtp_url), this option does nothing: NeoMutt will never write out the Bcc: header in this case.

Note

Only affects the sending of messages. Fcc’ed copies of a message will always contain the Bcc: header if one exists.