mailcrypt-3.5.6 released

[<war...@lo...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've just finished releasing mailcrypt-3.5.6. The only major change is a
one-character (literally!) regexp fix that was preventing mailcrypt from
working with gnupg-1.0.5 (the latest release). I've also updated the docs to
point to the new MailCrypt home on sourceforge
(http://mailcrypt.sourceforge.net), and along the way picked up some bug fixes
that have been in CVS for quite a while without ever getting released.

This is the first version released off the sourceforge CVS tree, and my first
attempt at a mailcrypt release. Please let me know if I missed anything.

The release is available from the sourceforge download page at
<http://sourceforge.net/project/showfiles.php?group_id=397> (although
<http://prdownloads.sourceforge.net/mailcrypt/> is slightly more direct).

 md5sum mailcrypt-3.5.6.*
 927cdd34882c490aa0fe0ac91b9d599c  mailcrypt-3.5.6.sig
 3078e0674f70a345217799f623a5a436  mailcrypt-3.5.6.tar.gz

The release is signed (mailcrypt-3.5.6.sig) with my (DSA) public key
0x4B71C44E, available from the keyservers or my personal home page at
<http://www.lothar.com/warner-gpg.html>.

I'm looking for someone(s) to help maintain the PGP side of mailcrypt,
especially folks who are interested in the newer versions of PGP (>5), since I
don't use them myself. There are also lots of bugs to fix and features to add
(proper MIME support is high on the list). Feel free to join in the fun!

NEWS entry attached below. Please feel free to forward this to any lists that
seem appropriate.

Share and Enjoy!
 -Brian <war...@lo...>


================================================

Noteworthy changes in Mailcrypt version 3.5.6:

 * Fix to work with GnuPG-1.0.5.

 * Update docs to point to new home on SourceForge.

 * Changes that have been languishing in CVS for, um, ages. (18 months? eek!)

   * Bugfix in mh-rmail support.  Len's note says it "dropped the user into a
     stupid buffer after decrypting a message".

   * Bugfix in RMAIL "signature verified" status indicator (the "verified"
     label). Old code got the flag backwards if you chose to replace the
     encrypted message with the decrypted plaintext.  New code fixes that and
     marks the message decrypted (and verified, if appropriate) even if you
     just view it without replacing the original.

 * Minor build fixes.

================================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/>

iD8DBQE7ChuRLnyKqEtxxE4RAj5RAKDW+b8IQq2YxKv2f8yH9Xxd0+NBhACgxvAm
xWXqGFqgE9re8djzFiftA+c=
=D6fL
-----END PGP SIGNATURE-----