Pine 4.64 is now available

This note is to announce the availability of the Pine Message System
version 4.64.  This is a maintenance release with only a few new features.

Specific information about changes can be found in the built-in release
notes ("R" off the Main Menu), or via any of:

           http://www.washington.edu/pine/

           http://www.washington.edu/pine/changes.html

           ftp://ftp.cac.washington.edu/pine/docs/


UNIX source code for the latest Pine release is available at:

           http://www.washington.edu/pine/getpine/
or
           ftp://ftp.cac.washington.edu/pine/pine.tar.gz
                 (MD5: 9cc68749675f1c35a2147a35d2c5b344)
           ftp://ftp.cac.washington.edu/pine/pine.tar.Z
                 (MD5: 75af127948cc0c701d424d22d621f792)
           ftp://ftp.cac.washington.edu/pine/pine.tar.bz2
                 (MD5: 39ca07b3d305b4cd0d6aaf4585123275)

Pre-built binaries are available for a small number of UNIX operating
environments via:

           http://www.washington.edu/pine/getpine/

The PC-Pine distribution is also available at the above url, or at:

           ftp://ftp.cac.washington.edu/pine/pcpine/setup_pine_4.64.exe
                 (MD5: 7cf8533644d15107e25269b8571b8bd8)

Alternatively, the zip file is also available at:

           ftp://ftp.cac.washington.edu/pine/pcpine/pm464w32.zip
                 (MD5: dfae9d81a6a0b6abffc8de56f931dd64)

Linux RPMs and Debian packages are also available at:

           http://www.washington.edu/pine/getpine/linux.html
or
           ftp://ftp.cac.washington.edu/pine/pine-4.64-1.i386.rpm
                  (MD5: 78cb63eb00769c4390d71a5d725caff2)
           ftp://ftp.cac.washington.edu/pine/pine-4.64-1.src.rpm
                  (MD5: 5c5122e256acb8302e76d8f83f7f11ad)
           ftp://ftp.cac.washington.edu/pine/pine_4.64_i386.deb
                  (MD5: 4cdc6c60dbe8e47829189194b8cbd99a)

New enhancements in version 4.64 include:

      * Even though Pine does not properly support the UTF-8 character
        set, the Allow-Version3-LDAP feature will cause Pine to go ahead
        and try to talk to an LDAP server which is a version 3 server. You
        will find this feature in the Setup/Directory screen. It is
        separately settable for each server you configure.

Some of the bugs that have been addressed in this release include:

      * Crash with malformed mailbox name that allows an authorized user
        to run commands from the shell
      * When a PC-Pine network read, or a non-SSL Unix Pine network read
        took longer than Tcp-Read-Warning-Timeout (default 15 seconds)
        Pine would always time out instead of allowing the user to
        continue
      * Bug when setting Reply-Indent-String to the Empty Value. Quote
        showed up as a double quote instead of as nothing.
      * Crash when Pine attempts to open a remote (IMAP, POP3, NNTP)
        mailbox specification that has an unterminated quoted string in
        the network part of the name
      * Sorting by Score would not work after changing a message's score
        by setting a keyword or changing its status
      * Crash when adding then deleting the first header color
      * Crash when Bouncing a message and then selecting the address to
        bounce the message to using ^T and the directory server screen
      * When exporting a flowed message, perform wrapping to get rid of
        long lines and space stuffing
      * Incorrect MESSAGE INDEX when message contains some high-bit
        characters (do a better job of ensuring that control characters in
        a message don't reach the screen by mistake)
      * Limit amount of delay that can be caused by the system clock
        jumping backwards
      * Bug that caused confirmation prompt to be skipped when Apply
        Saving messages with the first message in the set not having
        deleted parts
      * Allow commas in Customized-Hdrs fields and in header fields
        defined in Roles
      * When two Pines were accessing the same address book and the two
        Pines had different ideas of how it should be sorted, they could
        get into a slow loop changing the sort order back and forth
        forever. Now give up and leave the sort alone after the first time
        this happens in a session.
      * When Disable-Keymenu was set the "Other" subcommand did not work
        correctly in the Apply command
      * When an address book contained multiple entries with the same
        nickname the ^T method of selecting always selected the first
      * Crash when editing the first of two address book entries with the
        same nickname and changing the first from a single address into a
        list of addresses

As with all Pine releases, it is important that you carefully test and
determine for yourself that it performs suitably in your environment
before placing Pine into production use.

The Pine Development Team
_______________________________________________
Pine-announce mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-announce