1. 21

Release announcement:

Hi Mutt Users,

I’ve just released version 1.10.1. Instructions for downloading can be found at http://www.mutt.org/download.html.

This is a bug fix release, and includes a few important security fixes. I strongly recommend IMAP and POP users upgrade as soon as possible.

This release merits special thanks to a couple security researchers.

Jeriko One discovered a host of vulnerabilities in the IMAP and POP code. His bug reports were detailed, and included demonstration code and suggested fixes.

Marcus Brinkmann discovered an issue with encrypted email spoofing, and reported the issue to GnuPG and Mutt. There is a new option $pgp_check_gpg_decrypt_status_fd to check for this. If you have any issues, please check your configuration against contrib/gpg.rc.

Also, thanks is due to Richard Russon. An unfortunately timed absence left me scrambling to get the fixes in. Richard kindly shared his patches and delayed his release until today, to give me time to prepare the release.

Lastly, a big thanks to everyone who helped work on this release!

-Kevin

  1.  

  2. 4

    I am amazed that mutt is still alive and kicking. Fond memories of another Internet

    1. 4

      It’s very much alive and kicking - there’s even NeoMutt, a fork with added features. As someone who’s used Mutt/NeoMutt almost every day for 20+ years, it’s still very much useable today. Yes, HTML email does make things a bit painful, but there are workarounds.

      1. 1

        I’m using a stripped down version of elinks to do HTML -> plaintext conversions, both for mail and some other projects. w3m is also popular for this task.

        Do you have other solutions you’d like to share?

        1. 3

          I’m using pretty much the same, albeit with w3m. I use a modified version of view_attachment.sh to handle attachments (grabbed from The Homely Mutt - there are plenty of other great tips in that article).

          1. 1

            Thanks. I’m working on a bidirectional mail gateway which does Unicode/MIME/RFC-5322/RFC-6854 <—> ASCII-ANSI-X3.4-1986/RFC-822 conversions.

            Converting MIME/Base64 encoded parts into to UUENCODE and back is straightforward (and lossless).

            The lossy transliteration of Unicode characters into plaintext equivalents is less straightforward and there is a wealth of prior art.

            The task of ceating a usable presentation of modern HTML mail as plaint text, however, is more of an art than a science.

          2. 2

            FWIW urlscan is another useful tool https://github.com/firecat53/urlscan

            In mutt I bind this to C-b so I can quickly open some link in my browser

        2. 2

          I’m actually still an elm user, myself.

          1. 2

            I also still use it. Works great, no nonsense. Sure, when I want to see an image I have to scp it to my local system, but hey :)

          2. 2

            I’m glad we still have such a stripped-down email implementation being kept up. I’d probably only use it in cases where I needed the extensibility though, as automatic email filtering is far too big a boon to give up.

            1. 4

              You can always use Sieve on the IMAP side, or fdm, maildrop, or the venerable procmail for local filtering.

              1. 2

                Honestly I find notmuch to be a better filtering/tagging system than all of my gmail filters.

                1. 1

                  To clarify: I’m specifically thinking of Inbox.