.`mutt` rebased to version 2.0.7 The `Mutt` email client has been updated to version 2.0.7, which provides a number of enhancements and bug fixes. Notable changes include: * `Mutt` now provides support for the `OAuth 2.0` authorization protocol using the `XOAUTH2` mechanism. Mutt now also supports the `OAUTHBEARER` authentication mechanism for the IMAP, POP, and SMTP protocols. The OAuth-based functionality is provided through external scripts. As a result, you can connect `Mutt` with various cloud email providers, such as `Gmail` using authentication tokens. For more information on how to set up `Mutt` with OAuth support, see link:https://access.redhat.com/articles/6278361[How to set up Mutt with Gmail using OAuth2 authentication]. * `Mutt` adds support for domain-literal email addresses, for example, `user@[IPv6:fcXX:...]`. * The new `$ssl_use_tlsv1_3` configuration variable allows TLS 1.3 connections if they are supported by the email server. This variable is enabled by default. * The new `$imap_deflate` variable adds support for the `COMPRESS=DEFLATE` compression. The variable is disabled by default. * The `$ssl_starttls` variable no longer controls aborting an unencrypted IMAP `PREAUTH` connection. Use the `$ssl_force_tls` variable instead if you rely on the `STARTTLS` process. Note that even after an update to the new `Mutt` version, the `ssl_force_tls` configuration variable still defaults to `no` to prevent RHEL users from encountering problems in their existing environments. In the upstream version of `Mutt`, `ssl_force_tls` is now enabled by default.