Commit 3a6f7bb9 authored by Antonio Radici's avatar Antonio Radici

removing debian/ from upstream

parent cc4009f0
Only in ../m/debian/mutt/usr/share/doc/mutt: BUGS.IMAP
Only in ../m/debian/mutt/usr/share/doc/mutt: README.IMAP
Only in ../m/debian/mutt/usr/share/doc/mutt: TODO.IMAP
Only in debian/mutt/usr/share/doc/mutt/examples: ca-bundle.crt
Only in debian/mutt/usr/share/doc/mutt/examples: iconv
Only in debian/mutt/usr/share/doc/mutt/examples: smime_keys_test.pl
mutt (1.5.17-2) unstable; urgency=low
There is now a "mutt-patched" package that will contain some more
experimental patches. For now that is the "sidebar" patch. See
README.Patches for details.
-- Christoph Berg <myon@debian.org> Tue, 01 Jan 2008 20:03:16 +0100
mutt (1.5.16-2) unstable; urgency=low
User-visible changes in this version:
* The gpgme crypt backend is not yet stable enough, disabled again.
* The imap_home_namespace variable was removed upstream.
-- Christoph Berg <myon@debian.org> Thu, 28 Jun 2007 20:58:49 +0200
mutt (1.5.14+cvs20070301-1) experimental; urgency=low
We no longer unset write_bcc in /etc/Muttrc. If your MTA does not strip Bcc:
headers, edit /etc/Muttrc. (exim4 and postfix strip them, exim(3) does not.)
We also no longer unset use_from and use_domain. Mutt will use the contents
of /etc/mailname to determine the domain part of the From: header.
This release adds ESMTP support to mutt. To use, set smtp_url to your
smarthost, e.g. smtps://mail.company.com/.
The gpgme crypt backend is now enabled.
-- Christoph Berg <myon@debian.org> Thu, 1 Mar 2007 23:56:58 +0100
mutt (1.5.6-1) unstable; urgency=low
In this release the alternates, lists, and subscribe configuration
variables have been turned into regular expression lists.
Additionaly, alternates is now an option, not a variable.
This means that you should change:
set alternates="foo|bar"
into
alternates "foo|bar"
in your .muttrc file. See muttrc(5) for details.
-- Artur R. Czechowski <arturcz@hell.pl> Sun, 4 Apr 2004 14:04:03 +0200
l10n support
~~~~~~~~~~~~
If you want to see non-ASCII characters on a Debian system, there's no
use fiddling with the variable "charset", as described in the manual
page muttrc(5).
Instead, you'll need to have the Debian package "locales" installed on
your system and set the LANG or LC_CTYPE environment variable.
e.g. US users will want to add "export LC_CTYPE=en_US" to their ~/.bashrc.
If you have a /etc/locale.gen file read carefully the comment and do
what it says, or it will not work.
No, linux systems do not need --enable-locales-fix or --without-wc-funcs,
so don't bother me saying these switches cure your problems.
PGP support
~~~~~~~~~~~
GnuPG support works out of the box with the default /etc/Muttrc.
You do not need any of the example files in /usr/share/doc/mutt/
unless you plan to send signed+encrypted messages to pgp2 users.
gpg-2comp
~~~~~~~~~
/usr/share/doc/mutt/examples/gpg.rc uses a wrapper program called
gpg-2comp which is not available as a debian package.
This program is needed only to sign and encrypt messages with a method
compatible with PGP 2.x. Users who don't need this feature can use the
commands provided in the default /etc/Muttrc.
The pgpewrap and pgpring programs used by some example rc files have
been installed in /usr/lib/mutt.
The files /usr/share/doc/mutt/examples/*.rc are just examples and are not
supposed to be used as is. Actually they are not supposed to be used at
all, PGP support works out of the box if gnupg is installed.
GnuPG passphrase
~~~~~~~~~~~~~~~~
The GnuPG passphrase is not asked if the $GPG_AGENT_INFO environment
variable exists.
Scripts
~~~~~~~
Look at /usr/lib/mutt/{debian-ldap-query,mailspell}.
pgp_encryptself
~~~~~~~~~~~~~~~
This mutt 1.0.x configuration option does not exist anymore and this
will not change. To achieve the same effect you can add something like
--encrypt-to=your@mail.address to the relevant ~/.muttrc configuration
lines (pgp_encrypt_only_command and pgp_encrypt_sign_command) or to
~/.gnupg/options .
S/MIME Support
~~~~~~~~~~~~~~
See README.SMIME for details.
About temporary files and security
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When using mutt to view an encrypted message, the plain text is saved in
a temporary file. If you have reasons to worry an attacker may recover
the deleted file from your hard disk please take appropriate actions to
prevent this (e.g. use a ramdisk or shred(1) or wipe(1)).
Also don't forget about the temporary files created by your editor.
Mutt creates temporary files in a secure way. See #222125 for details.
/etc/Muttrc.d/
~~~~~~~~~~~~~~
The default /etc/Muttrc will source more configuration directives from
files in the /etc/Muttrc.d/ directory ending in ".rc".
The system administrator may use the directory for local customizations
and packages enhancing mutt may use it to install their configuration
directives.
The directory is processed last in /etc/Muttrc, so that settings there
may override the defaults from the file.
-- Christoph Berg <myon@debian.org> Sat, 03 Nov 2007 21:02:26 +0100
This package uses quilt to manage all modifications to the upstream
source. Changes are stored in the source package as diffs in
debian/patches and applied during the build.
To configure quilt to use debian/patches instead of patches, you want
either to export QUILT_PATCHES=debian/patches in your environment
or use this snippet in your ~/.quiltrc:
for where in ./ ../ ../../ ../../../ ../../../../ ../../../../../; do
if [ -e ${where}debian/rules -a -d ${where}debian/patches ]; then
export QUILT_PATCHES=debian/patches
fi
done
To get the fully patched source after unpacking the source package, cd to
the root level of the source package and run:
quilt push -a
The last patch listed in debian/patches/series will become the current
patch.
To add a new set of changes, first run quilt push -a, and then run:
quilt new <patch>
where <patch> is a descriptive name for the patch, used as the filename in
debian/patches. Then, for every file that will be modified by this patch,
run:
quilt add <file>
before editing those files. You must tell quilt with quilt add what files
will be part of the patch before making changes or quilt will not work
properly. After editing the files, run:
quilt refresh
to save the results as a patch.
Alternately, if you already have an external patch and you just want to
add it to the build system, run quilt push -a and then:
quilt import -P <patch> /path/to/patch
quilt push -a
(add -p 0 to quilt import if needed). <patch> as above is the filename to
use in debian/patches. The last quilt push -a will apply the patch to
make sure it works properly.
To remove an existing patch from the list of patches that will be applied,
run:
quilt delete <patch>
You may need to run quilt pop -a to unapply patches first before running
this command.
package-status: mutt mutt-patched mutt-dbg
#!/bin/sh
echo "Including output of \`mutt -v'..."
LC_ALL=C mutt -v >&3
This diff is collapsed.
Source: mutt
Section: mail
Priority: standard
Maintainer: Christoph Berg <myon@debian.org>
Uploaders: Adeodato Simó <dato@net.com.org.es>, Antonio Radici <antonio@dyne.org>
Build-Depends: debhelper (>> 5), quilt, automake, gawk, gettext, xsltproc,
docbook-xml, docbook-xsl, links, libncurses5-dev, libsasl2-dev, libgnutls-dev,
libidn11-dev, zlib1g-dev, libncursesw5-dev, libgdbm-dev, libkrb5-dev
Standards-Version: 3.8.0
XS-Vcs-Git: git://git.debian.org/git/pkg-mutt/mutt.git
XS-Vcs-Browser: http://git.debian.org/?p=pkg-mutt/mutt.git
Homepage: http://www.mutt.org/
Package: mutt
Architecture: any
Priority: standard
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: exim4 | mail-transport-agent, locales, mime-support, libsasl2-modules
Suggests: urlview, aspell | ispell, gnupg, mixmaster, openssl, ca-certificates
Provides: mail-reader, imap-client
Conflicts: mutt-utf8
Replaces: mutt-utf8
Description: text-based mailreader supporting MIME, GPG, PGP and threading
Mutt is a sophisticated text-based Mail User Agent. Some highlights:
.
* MIME support (including RFC1522 encoding/decoding of 8-bit message
headers and UTF-8 support).
* PGP/MIME support (RFC 2015).
* Advanced IMAP client supporting SSL encryption and SASL authentication.
* POP3 support.
* ESMTP support.
* Message threading (both strict and non-strict).
* Keybindings are configurable, default keybindings are much like ELM;
Mush and PINE-like ones are provided as examples.
* Handles MMDF, MH and Maildir in addition to regular mbox format.
* Messages may be (indefinitely) postponed.
* Colour support.
* Highly configurable through easy but powerful rc file.
Package: mutt-patched
Architecture: any
Priority: extra
Depends: ${shlibs:Depends}, mutt (= ${binary:Version})
Description: the Mutt Mail User Agent with extra patches
Mutt is a sophisticated text-based Mail User Agent.
.
This package adds the "sidebar" patch that lists mailboxes with new mail
in a separate column on screen.
Package: mutt-dbg
Architecture: any
Priority: extra
Depends: ${shlibs:Depends}, mutt (= ${binary:Version})
Description: debugging symbols for mutt
Mutt is a sophisticated text-based Mail User Agent.
.
This package contains the debugging symbols for mutt and mutt-patched.
This is Debian's prepackaged version of Mutt, a powerful text-mode mail
user agent.
The current maintainers for this package are:
Adeodato Simó <dato@net.com.org.es>
Christoph Berg <myon@debian.org>
Previous maintainers were:
Stephen Pitts <pitts2@memphisonline.com>
J.H.M. Dassen <jdassen@wi.LeidenUniv.nl>
Marco d'Itri <md@linux.it>
Original source has been downloaded from ftp://ftp.mutt.org/mutt/:
URL:<ftp://ftp.mutt.org/mutt/devel/>
The following copyright notices apply to most of the program. Some
modules are under different licenses, or in the public domain.
Please note that this is by no means an exhaustive list of all the
persons who have been contributing to this program. Please see the
manual for a (probably still non complete) list of the persons who
have been helpful with the development of this program.
Copyright (C) 1996-2007 Michael R. Elkins <me@cs.hmc.edu>
Copyright (C) 1996-2002 Brandon Long <blong@fiction.net>
Copyright (C) 1997-2008 Thomas Roessler <roessler@does-not-exist.org>
Copyright (C) 1998-2005 Werner Koch <wk@isil.d.shuttle.de>
Copyright (C) 1999-2009 Brendan Cully <brendan@kublai.com>
Copyright (C) 1999-2002 Tommi Komulainen <Tommi.Komulainen@iki.fi>
Copyright (C) 2000-2004 Edmund Grimley Evans <edmundo@rano.org>
Copyright (C) 2006-2008 Rocco Rutte <pdmef@gmx.net>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
Contributors:
Copyright (C) 2001 Marco d'Itri
Copyright (C) 2001-2002 Oliver Ehli
Copyright (C) 2004 Brian Fundakowski Feldman
Copyright (C) 2004 g10 Code GmbH
Copyright (C) 2004 Thomas Glanzmann
Copyright (C) 2003 Bjoern Jacke
Copyright (C) 2000 Manoj Kasichainula
Copyright (C) 2001-2004 Andrew McDonald
Copyright (C) 2001 Mike Schiraldi
Copyright (C) 2000-2003 Vsevolod Volkov
Copyright (C) 2004 Tobias Werth
Copyright (C) 2005 Andreas Krennmair <ak@synflood.at>
Copyright (C) 2005 Peter J. Holzer <hjp@hjp.net>
intl subdirectory:
Copyright (C) 1995-2001 Free Software Foundation, Inc.
Contributed by Ulrich Drepper, 1995.
On Debian systems, the complete text of the GNU General Public License
can be found in `/usr/share/common-licenses/GPL'.
md5c.c:
Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
rights reserved.
License to copy and use this software is granted provided that it
is identified as the "RSA Data Security, Inc. MD5 Message-Digest
Algorithm" in all material mentioning or referencing this software
or this function.
License is also granted to make and use derivative works provided
that such works are identified as "derived from the RSA Data
Security, Inc. MD5 Message-Digest Algorithm" in all material
mentioning or referencing the derived work.
RSA Data Security, Inc. makes no representations concerning either
the merchantability of this software or the suitability of this
software for any particular purpose. It is provided "as is"
without express or implied warranty of any kind.
These notices must be retained in any copies of any part of this
documentation and/or software.
The list of authors of the applied patches to this version of mutt can
be found in `/usr/share/doc/mutt/README.Patches'.
This file describes how to configure mutt to use S/MIME.
This file is almost the same as smime-notes.txt available in mutt upstream
sources, but it contains a few modifications about Debian-specific issues.
Mutt needs some user interaction to get it ready for S/MIME.
1. Make sure, that openssl (must be) and ca-certificates (recommended)
are installed. If not, ask your administrator to do it.
2. Run 'smime_keys init'.
3. If ca-certificates is installed, make a symlink:
ln -s /etc/ssl/certs ~/.smime/ca-bundle.crt
If not, there are some other packages which contain Root CA certificates,
for example: kdelibs-data, libcurl2.
This makes you trust anything that was ultimately signed by one of CA
included in symlinked crt file.
4. Get yourself a certificate. (You can get one for free from www.thawte.com,
or pay for one from VeriSign or one of its competitors). The way the
process generally works: the certificate will be installed "into" your web
browser. If you are asked what application you wish to use the
certificate with, select Netscape. Strangely enough, "mutt" is usually not
an option.
5. Assuming you are using Mozilla, follow the instructions at
www.verisignlabs.com/Projects/smime_docs/linux.html to export the
certificate into a file called cert.p12. If you don't use Mozilla, you're on
your own.
6. Run 'smime_keys add_p12 cert.p12'.
* When the script asks for the "Import password", enter the one you
provided when you exported the certificate
* When it asks for a "PEM pass phrase", make up a new password. Every
time you sign or decrypt a message, mutt will ask for the PEM passphrase
* Finally, when the script asks for a label, enter an easy-to-remember
name for the certificate, such as "me". The script output will include
a line like:
added private key: /home/raldi/.smime/keys/12345678.0 for raldi@verisignlabs.com
The number (including the ".0" at the end) is your keyid. You will
need this number in the next step.
7. Edit your .muttrc file and add a lines:
set smime_default_key=keyid
set smime_sign_as=keyid
Probably you also want to change default values for smime_timeout
and smime_encrypt_with originally set in global /etc/Muttrc
8. Optionally, you can add following line to your ~/.mailcap to view certificate
from mutt:
application/x-pkcs7-signature;openssl pkcs7 -in %s -inform der -noout -print_certs -text | pager; needsterminal
Last updated: Tue, 23 Dec 2003 22:35:40 +0100
Artur R. Czechowski <arturcz@hell.pl>
#!/usr/bin/perl -w
# by Ben Collins <bcollins@debian.org>, butchered by Marco d'Itri <md@linux.it>
# to use, add to ~/.muttrc:
# set query_command="/usr/lib/mutt/debian-ldap-query %s"
use strict;
my @attrs = qw(sn mn cn ircnick uid);
my $base = 'ou=users, dc=debian, dc=org';
my $server = 'db.debian.org';
my $port = 389;
die "Usage: $0 <name> [<name>...]\n" if not $ARGV[0];
eval 'require Net::LDAP;';
if ($@) {
$@ =~ s/ in \@INC.*/./;
die "Could not load Net::LDAP: $@\n" .
"(Warning: this script depends on the libnet-ldap-perl (>=0.22-1) package.)\n"
}
my $ldap = Net::LDAP->new($server, port => $port) or
die "Could not contact LDAP server $server:$port";
$ldap->bind or die 'Could not bind';
my @results;
foreach my $search (@ARGV) {
my $query = join '', map { "($_=*$search*)" } @attrs;
my $mesg = $ldap->search(
base => $base, filter => "(|$query)", attrs => [ @attrs ]
) or die 'Failed search';
foreach my $entry ($mesg->entries) {
my $uid = $entry->get_value('uid') || next;
my $fname = $entry->get_value('cn') || '';
my $mname = $entry->get_value('mn') || '';
$mname .= ' ' if $mname;
my $lname = $entry->get_value('sn') || '';
my $nick = $entry->get_value('ircnick')|| '';
push @results, "<$uid\@debian.org>\t$fname $mname$lname\t($nick)\n";
}
}
$ldap->unbind;
print 'Debian Developer query: found ', scalar @results, "\n", @results;
exit 1 if not @results;
exit 0;
#!/usr/bin/perl
#
# Wrapper to call ispell on mail messages, ignoring quoted portions
# and signatures.
# By Brendan O'Dea <bod@debian.org>, public domain.
# Usage: set ispell = /usr/lib/mutt/mailspell
#
use IO::File;
use POSIX 'tmpnam';
use File::Copy 'move';
$0 =~ s#.*/##;
my $ISPELL = 'ispell';
my $DIFF = 'diff';
my $ED = 'ed';
# make sure that we don't inherit SIGCHLD
$SIG{CHLD} = 'DEFAULT';
# ignore -x ispell option
shift if $ARGV[0] eq '-x';
die "Usage: $0 [-x] FILE\n" unless @ARGV == 1;
my $msg = $ARGV[0];
# create temporary files
my (%orig, %ed);
END {
unlink $ed{path} if $ed{path};
unlink $orig{path} if $orig{path};
}
foreach (\%orig, \%ed) {
$_->{path} = tmpnam;
$_->{fd} = IO::File->new($_->{path}, O_RDWR|O_CREAT|O_EXCL, 0600)
or die "$0: can't create $_->{path} ($!)";
}
while (<>) {
# stop at sigdashes
last if /^-- \n/;
# drop quoted text and attribution
$orig{fd}->print($_) unless /^>/ or /^On \w{3}, \w{3} \d{2}, \d{4} at \d/;
}
$orig{fd}->close;
my $pid = fork;
die "$0: can't fork ($!)\n" unless defined $pid;
unless ($pid) {
open STDOUT, '>&=' . $ed{fd}->fileno
or die "$0: can't dup stdout to ed script ($!)\n";
$ed{fd}->close;
exec $DIFF, '-e', $orig{path}, $msg;
die "$0: can't exec $DIFF ($!)\n";
}
die "$0: can't reap child ($!)\n" unless wait == $pid;
system $ISPELL, '-x', $orig{path}
and die "$0: problem with $ISPELL ($?)\n";
$ed{fd}->seek(0, SEEK_END);
$ed{fd}->print("w\nq\n");
$ed{fd}->seek(0, SEEK_SET);
open STDIN, '<&=' . $ed{fd}->fileno
or die "$0: can't dup stdin from ed script ($!)\n";
system $ED, '-s', $orig{path} and die "$0: problem with $ED ($?)\n";
move $orig{path}, $msg or die "$0: can't replace $msg ($!)\n";
delete $orig{path};
1;
#!/bin/sh -e
for rc in /etc/Muttrc.d/*.rc; do
test -r "$rc" && echo "source \"$rc\""
done
# vi: ft=sh
# Configuration for the sidebar patch.
# See /usr/share/doc/mutt/README.Patches for documentation.
ifdef sidebar_visible set sidebar_visible sidebar_width=20
/* XPM */
static char * mutt_xpm[] = {
"32 32 14 1",
" c None",
". c #CCCCCC",
"+ c #000000",
"@ c #7F7F7F",
"# c #B2B2B2",
"$ c #666667",
"% c #FF0000",
"& c #7F0000",
"* c #999999",
"= c #333333",
"- c #FF00FF",
"; c #FFFFFF",
"> c #7F007F",
", c #7F7F00",
" ",
" == ",
" ++ ",
" +..@@ ",
" +.,.+ ",
" + +.,.+ +++ ",
" + @+.,.+ +@@ ",
" @+ +....+++.@ ",
" +.@ @+.......+ ",
" +.+ +@....+.+ ",
" +.+ @+.....+.+ ",
" +.+@ +@........++++ ",
" +.@+ @+.........+;;> ",
" +..+++++++%@$#.......+.-- ",
" @@.@+&%&+@%%@@.......+>-> ",
" +..@+++@.@%%@$@......+++ ",
" +.........@%%+@$$....+ ",
" @@$.........@%%++@$..$+ ",
" +@@..........*%%++@@$+ ",
" +@@...........@%%++++ ",
" +@$............@+ ",
" +@@...#.......@+ ",
" @+@.#$+@@@...$++ ",
" +..$+@*@+..$+@+ ",
" @@.@++++++$.+@*+ ",
" @+..+*@@+=+@.+@.+ ",
" +@..+++@+++@..++@@+@ ",
" +@.....+@@+@.....+@.@ ",
" +$.....+@*+$.....+@.+ ",
" +@@.$..+@@+@@.$..+@.+ ",
" @++++++@++@++++++@++@ ",
" "};
# See /usr/share/doc/mutt/README.Debian for details.
source /usr/lib/mutt/source-muttrc.d|
# Some GB18030 traditional Chinese mails are wrongly labelled GB2312.
# The first charset is a superset of the second. Let's alias it, so
# that Mutt displays such mails as if they were correctly labelled.
charset-hook ^gb2312$ gb18030
# Some mailers send EUC-JP-MS Japanese mails wrongly labelled EUC-JP.
# The first charset is a superset of the second. Let's also alias it.
charset-hook ^euc-jp$ euc-jp-ms
# colors
color normal white black
color attachment brightyellow black
color hdrdefault cyan black
color indicator black cyan
color markers brightred black
color quoted green black
color signature cyan black
color status brightgreen blue
color tilde blue black
color tree red black
#color header brightgreen black ^From:
#color header brightcyan black ^To:
#color header brightcyan black ^Reply-To:
#color header brightcyan black ^Cc:
#color header brightblue black ^Subject:
#color body brightred black [\-\.+_a-zA-Z0-9]+@[\-\.a-zA-Z0-9]+
#color body brightblue black (https?|ftp)://[\-\.,/%~_:?&=\#a-zA-Z0-9]+
# Use folders which match on \\.gz$ or \\.bz2$ as [gb]zipped folders:
open-hook \\.gz$ "gzip -cd '%f' > '%t'"
close-hook \\.gz$ "gzip -c '%t' > '%f'"
append-hook \\.gz$ "gzip -c '%t' >> '%f'"
open-hook \\.bz2$ "bzip2 -cd '%f' > '%t'"
close-hook \\.bz2$ "bzip2 -c '%t' > '%f'"
append-hook \\.bz2$ "bzip2 -c '%t' >> '%f'"
# This color scheme aims to highlight as much useful information as
# possible without spoiling user's visual experience by irritating
# contrasts. Optimized for dark or transparent background.
# --Dmitry Borodaenko <angdraug@mail.ru>
# override defaults, make transparency work
color normal white default
color attachment green default #
color hdrdefault cyan default
color indicator black cyan
color markers brightred default
color quoted green default
color signature brightblue default #
color status brightgreen blue
color tilde brightblue default #
color tree red default
# paint different quote levels
color quoted green default
color quoted1 cyan default
color quoted2 yellow default
color quoted3 red default
color body brightred default "[\-\.+_a-zA-Z0-9]+@[\-\.a-zA-Z0-9]+" # email
color body brightblue default "(http|ftp)://[\-\.\,/+=&%~_:?\#a-zA-Z0-9]+" # URL
color body brightgreen default "(^| |[-.[:alnum:]]+:+)~?\(/[-_.'[:alnum:]]+\)+/?" # Unix file path
color body brightgreen default "(^| +)[[:alpha:]]:[-_.[:alnum:]\]+" # DOS file path
color body brightmagenta default "(^|[ '\"]+)\\$[[:alpha:]][-_[:alpha:]]+" # variable
color body brightred default "(^| )[*_]+[-&[:alnum:]]+[*_]( |$)" # bold/underline
color body yellow default "(^| )[;:8][-^o]?[)>(|/\\]+" # smiley
color body red default "[!?]{3,}" # exclamation
color body green default "^ *[-+*o] +" # list item
# date formats
color body cyan default "[0-9]{1,2}:[0-9]{2}(:[0-9]{2})?( ?(AM|PM|am|pm))?( +[+-][0-9]{4})?"
color body cyan default "(\(19|20\)?[0-9]{2}/[01]?[0-9]/[0123]?[0-9]|[0123]?[0-9][/.][01]?[0-9][/.]\(19|20\)?[0-9]{2})(( at)? +[0-9]{1,2}:[0-9]{2}(:[0-9]{2})?( ?(AM|PM|am|pm))?( +[+-][0-9]{4})?)?"
color body cyan default "((Sun(day)?|Mon(day)?|Tue(sday)?|Wed(nesday)?|Thu(sday)?|Fri(day)?|Sat(urday)?),? +)?(Jan(uary)?|Feb(ruary)?|Mar(ch)?|Apr(il)?|May|June?|July?|Aug(ust)?|Sep(ember)?|Oct(ober)?|Nov(ember)?|Dec(ember)?)[ .]+[0-9]{1,2}(st|nd|rd|th)?,?( +(19|20)[0-9]{2}(,?( at)? [0-9]{1,2}:[0-9]{2}(:[0-9]{2})?( ?(AM|PM|am|pm))?( +[+-][0-9]{4})?)?)?"
color body cyan default "((Sun(day)?|Mon(day)?|Tue(sday)?|Wed(nesday)?|Thu(sday)?|Fri(day)?|Sat(urday)?),? +)?[0-9]{1,2}(st|nd|rd|th)?[ .]+(Jan(uary)?|Feb(ruary)?|Mar(ch)?|Apr(il)?|May|June?|July?|Aug(ust)?|Sep(ember)?|Oct(ober)?|Nov(ember)?|Dec(ember)?),?( +(19|20)?[0-9]{2})?(( at)? [0-9]{1,2}:[0-9]{2}(:[0-9]{2})?( ?(AM|PM|am|pm))?( +[+-][0-9]{4})?)?"
color header brightgreen default ^From:
color header brightcyan default ^To:
color header brightcyan default ^Reply-To:
color header brightcyan default ^Cc:
color header brightblue default ^Subject:
color header brightcyan default "^newsgroups: "
color header yellow default "^Delivered-To: "
color header green default "^sender: "
color header green default "^organi[sz]ation: "
color header green default "x-editor: "
color header green default "(x-mailer|user-agent): "
color header green default "X-Operating-System: "
color header green default "X-MimeOLE: "
color header green default "X-Accept-Language: "
color header red default "^message-id:"
color header red default "^in-reply-to: "
color header red default "^references: "
color header cyan default "^followup-to: "
color header cyan default "^mail-followup-to: "
color header cyan default "^reply-to: "
color header magenta default "MIME-Version: "
color header magenta default "Content-Type: "
color header magenta default "Content-Transfer-Encoding: "
color header magenta default "Content-Disposition: "
color header magenta default "Content-Encoding: "
color header magenta default "Content-Language: "
color status brightwhite blue
color index brightblue default '~P' # from me
color index cyan default '~p' # personal
color index brightcyan default '~G' # PGP
color index brightred default '~F' # flagged
color index green default '~Q' # replied
color index brightwhite default '~N' # new
color index red default '~D' # deleted
# threads
#color index brightyellow default "~h 'References: +<.+>'"
#color index yellow default "~h 'References: +<.+> +<.+>'"
#color index brightred default "~h 'References: +<.+> +<.+> +<.+>'"
#color index red default "~h 'References: +<.+> +<.+> +<.+> +<.+>'"
#color index blue default "~h 'References: +<.+> +<.+> +<.+> +<.+> +<.+>'"
#color index green default "~h 'References: +<.+> +<.+> +<.+> +<.+> +<.+> +<.+>'"
# spam
color index magenta default "\(Resent-\)?Message-Id: <>"
color index magenta default "\(Resent-\)?Message-Id: '<.* .*>'"