**ANNOUNCE** HylaFAX 4.2.3 Now Available

"Darren Nickerson" <[email protected]> Mon, 14 Nov 2005 01:03:38 -0500
Newsgroups gmane.comp.telephony.fax.hylafax.announce
Message-ID <0cd701c5e8e1$284fc810$090a000a@dazzalap>
Folks,

 The HylaFAX development team is pleased to announce our 4.2.3
patch level release!  As always, our sincerest thanks go to all who
participate and provide feedback.

The source code for the 4.2.3 release can be downloaded from:

       ftp://ftp.hylafax.org/source/hylafax-4.2.3.tar.gz
      (md5: e72f381a766c58c692afdf42326dc4e6 1,449,095 bytes)

The README from this release follows. Please read it carefully.

                              *   *   *

This document is intended to describe the significant differences
between hylafax-4.2.3 and older releases, point out any known
incompatibilites and issues, and provide the reader with directions to
further resources regarding HylaFAX.

                         *   NEW FEATURES   *

* IXO/TAP page batching
* JBIG send support via ModemSoftRTFCC in Class 1/1.0 (requires
   JBIG-KIT library)
* Retransmit-Ignore, a new RTNHandlingMethod, is now the default
* numerous other enhancements and bugfixes (see CHANGES)

                        *   KNOWN ISSUES   *

** Please refer to HylaFAX Bugzilla for a detailed list of issues.

                      *   INCOMPATIBILITIES   *

* Some modem config files generated from earlier versions' config file
 prototypes may contain Class1TCFRecvHack.  This is no longer desireable
 for production use, and this feature should now only be used for
 debugging purposes.
* If upgrading from any release other than 4.2.2 directly, be advised that
 CIDName/CIDNumber are now part of a larger CallID framework.
* libtiff-3.6.1 is fatally flawed when dealing with Group 3 images.
   Don't use it as-is.
   See: http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=500

                     *   WHO SHOULD UPGRADE?   *

* For security reasons, everyone should consider upgrading to this 4.2.3
   release as soon as possible.
* Users of Class 1/1.0 devices should upgrade to benefit from ongoing
  work in this area
* Users who regularly send fax batches (first introduced in 4.2.0)
   should upgrade to get the fixes in 4.2.3.


                    *   HYLAFAX BINARY PACKAGES   *

Binary packages for some operating systems and platforms are available.
 Please see ftp://ftp.hylafax.org/binary/ and
 http://www.hylafax.org/howto/install.html#ss2.3.3  If you are able and
 willing to produce a binary package of HylaFAX for general distribution,
 then you are invited to join [email protected] and solicit your
 binary package.

                       *   SUPPORT   *

 HylaFAX has numerous public support resources available.  The user is
encouraged to utilize the manpage documentation before turning to
other support arenas.  However, if other support is desired, or if you
would like to actively take part in the HylaFAX community, you are
invited to:

 * join and participate in a HylaFAX mailing list
    See: http://www.hylafax.org/mailing-lists.html

    When corresponding about this software, please always specify:
    - what version of HylaFAX you have,
    - what system you're running on (if it is Linux please name the
      distribution)
    - if the problem is modem-related, identify it and the firmware rev
    For example: "HylaFAX v4.0pl2 under RedHat Linux 4.2 with gcc 2.7.2;
    ZyXEL 1496E with 6.11a firmware."

  * read the on-line documentation and resources
    See: http://www.hylafax.org and http://www.hylafax.org/howto

  * review HylaFAX CVS
    See: http://www.hylafax.org/cvs.html

  * report confirmed bugs, feature requests, and submit patches
    See: http://bugs.hylafax.org/bugzilla



 Thanks,

  The HylaFAX development team

 -------------------------------------------------------------------

 And now, a note from HylaFAX's original author ;-)

 Silicon Graphics has seen fit to allow me to give this work away.  It
 is free.  There is no support or guarantee of any sort as to its
 operations, correctness, or whatever.  If you do anything useful with
 all or parts of it you need to honor the copyright notices.   I would
 also be interested in knowing about it and, hopefully, be acknowledged.

 Finally, note that this software is called ``HylaFAX'', not ``Hylafax'',
 ``hylafax'', and certainly not ``FlexFAX'' (the old name which someone
 else has a copyright on).  If you want to refer to this software use
 ``HylaFAX (tm)'' and be sure to honor the Silicon Graphics trademark.

 Sam Leffler

 Use and Copyright
 -----------------

 Copyright (c) 1988-1996 Sam Leffler
 Copyright (c) 1991-1996 Silicon Graphics, Inc.
 HylaFAX is a trademark of Silicon Graphics

    Permission to use, copy, modify, distribute, and sell this software and
    its documentation for any purpose is hereby granted without fee, 
provided
    that (i) the above copyright notices and this permission notice appear 
in
    all copies of the software and related documentation, and (ii) the names 
of
    Sam Leffler and Silicon Graphics may not be used in any advertising or
    publicity relating to the software without the specific, prior written
    permission of Sam Leffler and Silicon Graphics.

    THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
    EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
    WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

    IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
    ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
    OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
    WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY 
OF
    LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
    OF THIS SOFTWARE.


____________________ HylaFAX(tm) Announce Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe [email protected] < /dev/null