The HylaFAX development team is pleased to announce our 4.1.1 patch-level
release!  The release represents countless hours of work and testing by
developers and contributors, and our thanks goes to all who participate and
provide feedback.

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

    ftp://ftp.hylafax.org/source/hylafax-4.1.1.tar.gz
    (md5: 8b9c8a7d6bf5c7f9777dd9e164b7fb10  1,259,307 bytes)

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

                               *   *   *

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

                          *   NEW FEATURES   *

* improved prototype config support for AT&T, Prometheus, MultiTech, 
  Hayes, Conexant, Boca, US Robotics, and Practical Peripherals modems
* 7-bit text support for typerules
* bulk faxes now drop in requeue priority rather than increase
* pass CIDNumber and CIDName through to faxgetty for CID/DNIS routing
* FILETYPE support in FaxDispatch (requires metamail when using TIFF/PDF)
* integrated Linux DSO support
* coverpage "from" options and faxcover behavior and documentation harmony
* added Class1SendMsgDelay and ModemSoftResetCmdDelay defaults and options
* added Class1EOPWaitCmd, Class1PPMWaitCmd, and Class1TCFWaitCmd in lieu 
  of Class1Send*Delay options which causes Class 1 modems to use +FTS 
  instead of software pauses in these instances.
* various other bugfixes, minor enhancements, and additions
** please refer to CHANGES for a detailed list of code changes

                         *   KNOWN ISSUES   *

* Specific support for fax classes 1.0 and 2.1 are not yet implemented.
* Server-based fax archival support is still unimplemented (although 
  documented).
* When running in Class 2/2.0, NSF can be parsed incorrectly.
* Copy quality checking by cqtest is imperfect.
* sendfax use of ~/.hylarc differs from its use of hyla.conf
* faxrm and faxalter contain format string vulnerabilities.
** Please refer to HylaFAX Bugzilla for a detailed list of issues.

                       *   INCOMPATIBILITIES   *

* The popular faxrcvd-mail scripts have been deprecated by FILETYPE use in 
  FaxDispatch, and unchanged, will not work with faxgetty in 4.1.1.  See 
 'man faxrcvd' for details.
* Failed faxes now have status "F" instead of "D".  Most client programs 
  which display/report job status will need some alteration to accomodate 
  this.
* HylaFAX 4.1.1 may not compile with gcc-3.0, and limited support is 
  available for Mac OS-X.

                  *   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 hylafax-devel@hylafax.org and solicit your 
binary package.

                          *   SUPPORT   *

HylaFAX has numerous 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