mutt: Text-based mailreader
Patches
Indexcolor Patch
This patch enables different colorings for different parts of the index display. For example you can choose one color for the subject, another one for the author, and a third one for the flags.
Screenshots:
- Screenshot #1: Just a random screenshot...
- Screenshot #2: Notice how messages written by me are differently colored then those from other authors. This is done using indexcolor's author pattern matching.
Downloads:
- mutt-1.5.12-indexcolor-3+cb.diff: indexcolor-3 forward-ported to mutt 1.5.12 by Christoph Berg. Thanks a lot!
- mutt-1.5.8-indexcolor-3.diff: Added pattern to indexauthor and indexcolor command. Documentation updates and some other fixes. This one is stable and has the biggest feature-set.
- mutt-1.5.8-indexcolor-2+cb.diff: -2 with additional fixes by Christoph Berg (thanks!). This one works really well.
- mutt-1.5.8-indexcolor-2.diff: Bugfix release
- mutt-1.5.8-indexcolor-1.diff: First release of the indexcolor patch. It's undocumented and buggy.
Tools
mutt-bug
This is a tool that displays Debian bug reports in mutt. You can then directly read all messages sent to the bug and reply. The messages are fetched directly from the web interface, so there is no delay between requesting bug and getting it per email.
This tool was originally written by Christoph Berg, I've made some modifications to make it work in arbitrary directories.
Useage:
mutt-bug bugnumber
Download: mutt-bug
gpgverify
gpg --verify is quite slow when you have large keyrings included (like the
debian keyring). This is nasty, since mutt has to wait until gpg is finished
when displaying a gpg signed message (with signature verification on). So I've
written a tool that splits a huge keyring into a lot of smaller keyrings (one
key per keyring) and a shell script to verify signatures, to be used
from within mutt. The former tool is called splitkeyring.sh. The
latter one is gpgverify.sh.
gpgverify.sh first invokes gpg --verify as normal and
captures its output. If gpg failed because the key was not found in any
keyring, the script looks if the key is in one of the splitted keyrings, and if
so, reruns gpg with that keyring included. Otherwise the gpg error is returned.
These scripts are still hacky, if you want to use them you'll probably have to modify them a bit. They aren't too big, so this shouldn't be too much of a problem.
Download: gpgverify
