Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#12100 closed enhancement (fixed)

mutt-1.12.0

Reported by: Douglas R. Reno Owned by: ken@…
Priority: normal Milestone: 9.0
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New minor version

Change History (4)

comment:1 by ken@…, 2 years ago

Owner: changed from blfs-book to ken@…
Status: newassigned

comment:2 by ken@…, 2 years ago

This file lists incompatible changes and additional/new features made to mutt. Please read this file carefully when upgrading your installation.

The description of changes are intentionally brief. For a more detailed explanation of features, please refer to the manual at http://www.mutt.org/doc/manual/

The keys used are:

!: modified feature, -: deleted feature, +: new feature

1.12.0 (2019-05-25)

! $ssl_use_tlsv1 and $ssl_use_tlsv1_1 now default to unset. + $auto_subscribe, when set, automatically adds an email with the List-Post

header to the subscribe list.

! Fcc now occurs after sending a message. If the fcc fails, mutt will prompt

to try again, or to try another mailbox.

+ Basic protected header ("memory hole") support added for the Subject header.

See the config vars: $crypt_protected_headers_read, $crypt_protected_headers_save, $crypt_protected_headers_subject, and $crypt_protected_headers_write.

! Color names can be prefixed with "light" in addition to "bright". "bright"

colors are bold face, while "light" are non-bold.

! Color commands can now include an attribute (e.g. bold, underline). ! $pgp_use_gpg_agent defaults set. + <descend-directory> in the browser menu allows entering nested maildir

directories.

+ <group-chat-reply> replies to all, but preserves To recipients in the reply. + $include_encrypted, default unset, prevents separately encrypted contents

from being included in a reply. This helps to prevent a decryption oracle attack.

! With gpgme >= 1.11, recipient keys with a trailing '!' now force subkey use,

as with classic gpg.

! In send mode, %{charset} mailcap expansion uses the current charset of the

file.

+ $imap_fetch_chunk_size allows fetching new headers in groups of this size.

This might help with timeouts during opening of huge mailboxes. If you have huge mailboxes, you should also try $imap_qresync.

! <toggle-write> can be invoked from the pager too. + The $forward_attachments quadoption allows including attachments in

inline-forwards (i.e. $mime_forward unset, $forward_decode set.)

comment:3 by ken@…, 2 years ago

Resolution: fixed
Status: assignedclosed

comment:4 by Bruce Dubbs, 2 years ago

Milestone: 8.59.0

Milestone renamed

Note: See TracTickets for help on using tickets.